-
Bug
-
Resolution: Unresolved
-
Critical
-
Pipelines 1.20.0
-
False
-
-
False
-
-
Description of problem:
tektonpruner configmap values are getting overrided after upgrade
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Install 1.19.3 operator
- Enable tektonpruner & update tekton-pruner-default-spec configmap with some values.
global-config: |- enforcedConfigLevel: global historyLimit: 8 failedHistoryLimit: 3 successfulHistoryLimit: 5
- Create few pipelineruns in test namespaces and validate pipelineruns are being pruned with the values set in configmap.
- Upgrade the operator to 1.20
- Once the operator upgrade is done, validate the values of tekton-pruner-default-spec configmap.
Actual results:
tekton-pruner-default-spec configmap values are getting overrided with default values as below.
global-config: | enforcedConfigLevel: global ttlSecondsAfterFinished: null successfulHistoryLimit: null failedHistoryLimit: null historyLimit: 100 namespaces: {}
Expected results:
The same data before upgrade should be retained in configmap even after upgrade
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
1.19.3_config_beforeupgrade.yaml
*
- blocks
-
SRVKP-7700 Reconciler and Controller based pruner for better performance - Enhancement for GA readiness
-
- Closed
-
- duplicates
-
SRVKP-8652 test
-
- Closed
-
-
SRVKP-8622 tektonpruner configmap values are getting overrided after upgrade
-
- Closed
-
-
SRVKP-8626 tektonpruner ConfigMap values are getting overridden after upgrade.
-
- Closed
-
-
SRVKP-8627 tektonpruner configmap values are getting overrided after upgrade
-
- Closed
-
- is related to
-
SRVKP-6990 Testing efforts for Pruner and Pruner related operator changes delivered in 1.20
-
- Closed
-