This repository has been archived by the owner on Jan 19, 2023. It is now read-only.
Fix Daemonset incorrectly showing status when pod is unavailable #2389
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.
What this PR does / why we need it:
The object status for daemonsets were checking against current number scheduled rather than desired number.
Which issue(s) this PR fixes
Not fixing the second point raised in that issue where warning and error status are sorted to the top because many objects can change status at once and cause a poor UX if elements on a datagrid were constantly moving.