vsphere-cloud-controller-manger only sets providerID on tainted nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vSphere Cloud Provider Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
According to upstream docs[0] concerning the cloud-manager indicate that when kubelet on a kubernetes node starts, it should have `--cloud-
* node.cloudprovi
To prevent scheduling workloads on this node until the cloud-provider is started. the vsphere-
It's possible to start charmed-kubernetes without a cloud-provider charm attached, but once the charm is started and related -- the nodes already enlisted into the cluster do not have this taint. Even restarting kubelet with the new argument `--cloud-
In order for the vsphere-
WORKAROUND:
Taint all the nodes once the vsphere-
> kubectl taint nodes --all node.cloudprovi
Changed in charm-vsphere-cloud-provider: | |
importance: | Undecided → Low |
status: | New → Triaged |