Description of problem:
tektonpruner ConfigMap values are getting overridden after upgrade.

Prerequisites (e.g., setup, operators/versions):

• Install 1.19.3 operator

• Enable tektonpruner and update the tekton-pruner-default-spec ConfigMap with custom values.

• Create a few PipelineRuns in test namespaces and validate they are being pruned using the custom values.

Steps to Reproduce:

1. Install operator version 1.19.3

1. Enable tektonpruner and modify tekton-pruner-default-spec ConfigMap

1. Create PipelineRuns in a test namespace

1. Upgrade the operator to 1.20

1. Check the values of tekton-pruner-default-spec after upgrade

Actual Results:
The tekton-pruner-default-spec ConfigMap values are getting overridden with default values.

Expected Results:
The same values in the ConfigMap before upgrade should persist after the upgrade.

Reproducibility:
Always

Acceptance Criteria:

• Custom values in ConfigMap are retained after upgrade

Definition of Done:

• Upgrade does not reset user-configured tektonpruner values

Build Details:

Additional Info:
Attached: tektonconfig and configmap files before & after upgrade.