vSphere cloud-controller-manager should tolerate not-ready taint #339
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
…e it is a system critical pod Signed-off-by: Andrew Sy Kim <kim.andrewsy@gmail.com>
k8s-ci-robot
added
cncf-cla: yes
|
/assign @dvonthenen |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dvonthenen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
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.
Signed-off-by: Andrew Sy Kim kim.andrewsy@gmail.com
What this PR does / why we need it:
vSphere cloud-controller-manager should tolerate the not-ready taint (which is applied when CNI is not applied yet) since it is considered a system critical pod.
Starting in v1.18 the "NotReady" condition which is typically applied when CNI on a node is not yet configured is now also a taint. We should ensure we tolerate this taint so the cloud provider can run prior to CCM starting up.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged):Fixes #334
Special notes for your reviewer:
Release note: