-
Notifications
You must be signed in to change notification settings - Fork 232
Fix: Pruner Config resetting to default when set to null #3078
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
Conversation
|
/kind bug |
|
/retest |
5f5b1cf to
bd44863
Compare
|
/lgtm |
|
@pramodbindal Attempt to upgrade from 0.77.x to the pr code base either results in pruner controller crashloop or configmap value not retained. Could you please assess the upgrade scenario once and confirm the outcome please. Thankyou |
|
/hold |
anithapriyanatarajan
left a comment
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.
@pramodbindal DeepCopyInto is causing the issue I believe. Could you consider this to get past the crashloop issue. Thankyou
|
LGTM |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anithapriyanatarajan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
|
/lgtm |
|
@dependabot rebase |
When HistoryLimit is set to null in tektonconfig then it resets back to 100 After this fix value will be retained This also fisxes the issues ot pruner confog resetting to default on upgrade. Now after upgrade pruner should retain the old config Restore Pre upgrade fucntions
|
/retest |
|
//lgtm |
|
/lgtm |
|
/cherry-pick release-v0.78.x |
1 similar comment
|
/cherry-pick release-v0.78.x |
|
✅ Cherry-pick to A new pull request has been created to cherry-pick this change to Please review and merge the cherry-pick PR. |
When HistoryLimit is set to null in tektonconfig then it resets back to 100
After this fix, value will be retained
This also fixes the issues of pruner config resetting to default on upgrade.
Now after upgrade pruner should retain the old config
Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make test lintbefore submitting a PRSee the contribution guide for more details.
Release Notes