Fix NodeNotHealthy alert with correct NodeNotReady taint #9470
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.
How to categorize this PR?
/area monitoring
/kind bug
What this PR does / why we need it:
This PR corrects the filtering query, as the current value v1beta1constants.LabelNodeCriticalComponent is wrong. The query was thought initially to handle
node.gardener.cloud/critical-components-not-ready
, hence the correct value should be v1beta1constants.TaintNodeCriticalComponentsNotReadyWhich issue(s) this PR fixes:
False alerts of nodes being reported as not healthy.
Special notes for your reviewer:
Release note: