Fix: Pruner Config resetting to default when set to null
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:
- [x] Run
make test lintbefore submitting a PR - [x] Includes tests (if functionality changed/added)
- [ ] Includes docs (if user facing)
- [x] Commit messages follow commit message best practices
See the contribution guide for more details.
Release Notes
NONE
/kind bug
/retest
/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
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
- ~~OWNERS~~ [anithapriyanatarajan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/hold cancel
/lgtm
@dependabot rebase
/retest
//lgtm
/lgtm
/cherry-pick release-v0.78.x
/cherry-pick release-v0.78.x
✅ Cherry-pick to release-v0.78.x successful!
A new pull request has been created to cherry-pick this change to release-v0.78.x.
Please review and merge the cherry-pick PR.