This change adds the ability to disable the vsphere cloud provider at installation time.
This is particularly useful for "mixed" clusters with both VM and Bare Metal Nodes. Adding Bare Metal nodes to a vSphere install is not a supported configuration, since the MachineConfig's will contain a kubelet argument specifying --cloud-provider=vsphere. This causes pod failures when the kubelet tries to mount a datastore PV on the node.
A new attribute was added to group_vars/all/yaml under the config: section named provider:
If this is absent or defined as anything other than none, the vsphere cloudprovider will be enabled. This maintains backwards compatibility.
vchintal
commented
4 years ago
This change adds the ability to disable the vsphere cloud provider at installation time.
This is particularly useful for "mixed" clusters with both VM and Bare Metal Nodes. Adding Bare Metal nodes to a vSphere install is not a supported configuration, since the MachineConfig's will contain a kubelet argument specifying
--cloud-provider=vsphere. This causes pod failures when the kubelet tries to mount a datastore PV on the node.A new attribute was added to
group_vars/all/yamlunder theconfig:section namedprovider:If this is absent or defined as anything other thannone, the vsphere cloudprovider will be enabled. This maintains backwards compatibility.