Enable the CCM to come up before node is ready so it can assign EIP. #246
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
deitch
previously approved these changes
Mar 31, 2022
Signed-off-by: Chris Privitere <cprivite@users.noreply.github.com>
cprivitere
force-pushed
the
tolerate-node-not-ready
branch
from
40d6ee9
to
d9e7dcc
Compare
deitch
approved these changes
Mar 31, 2022
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.
This PR adds a scheduling toleration for "node.kubernetes.io/not-ready". This is to enable the cloud provider to come up on the first control plane node of a brand new cluster and assign the EIP that will be used as the cluster's VIP for its API server. This behavior is needed for cluster-api style provisions without BGP.