1. What is the nature and description of the request?

Right now we can customize replica pod count in tekton-* deployments and it allows users to modify the replicas but as per the release notes the replica count would be reset when the Operator will upgrade.

If the update approval is automatic, It means that the user cannot expect when the configuration of the replica would be reset.

2. Why does the customer need this? (List the business requirements here)

To ensure the Pod replicas are present persistently even after the operator upgraded to achieve HA.

3. List any affected packages or components.

Below deployments are affected:

"tekton-pipelines-webhook, tekton-operator-proxy-webhook, tekton-pipelines-controller, tekton-triggers-controller, tekton-triggers-core-interceptors, tekton-triggers-webhook, tkn-cli-serve"