uninitialized taint should always be dropped
#8 258 ouverte le 9 mars 2023
Métriques du dépôt
- Stars
- (4 267 étoiles)
- Métriques de merge PR
- (Métriques PR en attente)
Description
Detailed Description
https://github.com/kubernetes-sigs/cluster-api/pull/7993 introduced the node.cluster.x-k8s.io/uninitialized:NoSchedule taint. This taint is applied by default to the nodes when CAPBK is used as the bootstrap provider. CAPI drops this taint from the nodes after the nodes are initialized (labels are synced).
This issue is to audit and ensure that the node is dropped by CAPI when using any of the Machine/MachinePool solutions.
- Machines
- MachinePoll
- MachinePool Machines
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
More context on the taint: The taint was introduced to solve the delay problem when syncing label to nodes to avoid unnecessarily scheduling workloads on wrong nodes. Part of proposal: Label Sync Between Machines and underlying Kubernetes Nodes
/kind feature