Skip to content

fix: max reconciliation interval applies after retry exhaustion #1491

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Sep 21, 2022

Conversation

csviri
Copy link
Collaborator

@csviri csviri commented Sep 20, 2022

No description provided.

@csviri csviri self-assigned this Sep 20, 2022
@csviri csviri force-pushed the max-delay-retry-issue branch from 0549899 to 95afaee Compare September 20, 2022 08:43
@csviri csviri changed the base branch from next to main September 20, 2022 08:43
@csviri csviri marked this pull request as ready for review September 20, 2022 11:21
@csviri csviri requested a review from metacosm September 20, 2022 11:21
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

95.5% 95.5% Coverage
0.0% 0.0% Duplication

@csviri csviri merged commit f4828e9 into main Sep 21, 2022
@csviri csviri deleted the max-delay-retry-issue branch September 21, 2022 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MaxReconciliationInterval is not triggered if the resource was never reconciled in the first place
2 participants