Tolerate CAPI node.cluster.x-k8s.io/uninitialized taint
#204
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Danil-Grigorev <[email protected]>
Danil-Grigorev
force-pushed
the
customize-tolerations
branch
from
2210a53 to
3641443
Compare
alexander-demicev
approved these changes
Mar 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CAPI taints nodes with
node.cluster.x-k8s.io/uninitializedtaint: https://cluster-api.sigs.k8s.io/developer/providers/contracts/bootstrap-config.html?highlight=taint#taint-nodes-at-creationThis taint is not getting removed until CCM is installed. This is a chicken and egg problem, since CAAPF installs CCM in this case, so it needs to roll out before and the taint blocks it.
This is reproducible in AWS kubeadm cluster, where a CCM installed via
Bundle.