-
Notifications
You must be signed in to change notification settings - Fork 38.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vshere cloud provider on the controller-manager fails to start on non-vmware hosts #65145
Comments
/sig vmware |
@alvaroaleman can you please share some more context- Why do you want vSphere cloud provider to work with non-vmware host (I believe you mean ESXi)? Where is this requirement coming from. |
@prashima We are building a Kubernetes cluster management solution which does Kubernetes in Kubernetes and works by creating the control planes in one cluster, then creating worker instances on one of the supported platforms, among them vsphere. Currently the cluster hosting the control planes (We call it seed cluster) has to run on ESXi, otherwise the controller-manager crashes. Having the check in place for the Kubelets is completely fine and definitely makes sense, but for the controller-manager it should IMHO not be required. |
…cloud Automatic merge from submit-queue (batch tested with PRs 65152, 65199, 65179, 64598, 65216). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Do not query for VMUUID in vsphere cloud provider if it was explicitly passed **What this PR does / why we need it**: It allows running the kube controller-manager with the vsphere cloudprovider enabled on a machine that is not a vmware VM **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes #65145 **Special notes for your reviewer**: **Release note**: ```release-note In the vSphere cloud provider the `Global.vm-uuid` configuration option is not deprecated anymore, it can be used to overwrite the VMUUID on the controller-manager ``` /sig vmware
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Currently the vsphere cloud provider blocks the controller-manager from running if its running on a non-vmware host, because it reads
/sys/class/dmi/id/product_serial
and checks if its content starts withVMWARE-
.What you expected to happen:
The controller manager to start
How to reproduce it (as minimally and precisely as possible):
Start a
controller-manager
on a non-vmware environment with the--cloud-provider vsphere --cloud-config /my/cloud/conf
flags setAnything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: