0

I'm working with a Rancher-managed Kubernetes cluster consisting of Linux nodes, all of which are in the "Running" state. I'm trying to install the Cloud Provider Interface (CPI) and Container Storage Interface (CSI) drivers through UI. The installation process appears to deploy the application, but the associated DaemonSet remains in the "In Progress" state.

Upon inspecting the DaemonSet, I found that the pods are stuck in a "CrashLoopBackOff" state. Checking the pod logs, I encountered the following error messages:

Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.

failed to create listener: failed to listen on 0.0.0.0:10260: listen tcp 0.0.0.0:10260: bind: address already in use.

What could be causing these issues, and how can I resolve them to successfully deploy the CPI and CSI drivers on my cluster?

Riyo
  • 1

1 Answers1

0

The underlying issue is, that all kubernetes cloud providers tried to bind the webhook ports 10258 and 10260 - even if you left them unconfigured. This was fixed in september last year and should be included in the vSphere cloud provider soon™.

As a temporary fix, you may include the argument --webhook-secure-port=0 in your container spec.

Eleasar
  • 388