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
[DNM] refactor backup CR related logic #3723
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3723 +/- ##
==========================================
+ Coverage 62.32% 62.35% +0.02%
==========================================
Files 165 165
Lines 17799 17805 +6
==========================================
+ Hits 11093 11102 +9
+ Misses 5631 5629 -2
+ Partials 1075 1074 -1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please update the test result to the PR description.
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/test pull-e2e-kind |
What problem does this PR solve?
Found backup CR cleaning related logic confusing.
What is changed and how does it work?
Refactored some function with identical behavior.
Code changes
Tests
Unit test
E2E test
Manual test
test backup using following yaml (dumpling)
backup succeeded
test backup using following yaml (br)
backup succeeded
test backup using following yaml (dumpling)
Backup succeeded. When backup deleted, data on s3 deleted
test backup schedule with cleanPolicy Retain (br)
a new backup will be created every minute, last backup deleted
No code
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.