Skip to content

Conversation

@rahulait
Copy link
Contributor

What this PR does / why we need it:
This PR makes sure we don't reset condition severity from error to warning during next reconciles. Last transition time for condition changes when its updated from warning to error. During next reconcile, if we look at the last reconcile time only, then it will be the updated time and current logic was assuming that time limit has not been reached and was flipping the condition back from error to warning.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@rahulait rahulait force-pushed the fix-record-decaying-condition branch 4 times, most recently from 0fa85fa to dd2b2d5 Compare November 20, 2024 18:41
@rahulait rahulait force-pushed the fix-record-decaying-condition branch from dd2b2d5 to cc44ce1 Compare November 20, 2024 19:03
@rahulait rahulait merged commit feafbed into main Nov 20, 2024
@AshleyDumaine AshleyDumaine deleted the fix-record-decaying-condition branch November 20, 2024 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants