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.
kube-node-ready
has lost its usefulness for several reasons:kube-node-ready
was introduced at a time where we had a problem that ASGs could be automatically AZ reblanced, terminating nodes before the replacements had a chance to startup. Having nodes only marked ready in the ASG once the kube-node-ready pod was running slowed this rebalancing down. We no longer have AZ rebalance enabled, so not relevant.This PR introduces a config-item
kube_node_ready_enabled
which lets us disable it. The intention is to first disable in test clusters and later in all clusters.This is indirectly motivated by switching to IMDSv2 for which
kube-node-ready
is not compatible with.