Set priority class for AWS CCM addon #11834
Merged
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.
External cloud provider will add a taint
node.cloudprovider.kubernetes.io/uninitialized
with an effect NoSchedule during initialization. This effectively blocks cluster initialization until the cloud controller manager is ready, so it should have higher priority.As an important side-effect of adding priority class, kOps validation will track status of AWS CCM pods.
/cc @olemarkus @rifelpet