Hub cluster result upstream

[ab-ghosh]

Changes

When multicluster is enabled (multi-cluster-disabled: false) and the cluster role is set to Hub (multi-cluster-role: Hub), automatically set replicas to 0 for tekton-results-watcher and tekton-results-retention-policy-agent deployments.

On a Hub cluster:

• The watcher is not needed as there are no local pipeline runs to watch
• The retention-policy-agent is not needed as cleanup happens on Spoke clusters

This is achieved by injecting deployment options in GetTektonResultCR() when creating the TektonResult CR from TektonConfig, leveraging the existing options mechanism.

• Inject deployment options to set replicas=0 for watcher and retention-policy-agent on Hub clusters
• Add unit tests for the hub cluster result configuration
• Add e2e tests for the hub cluster result configuration

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Run make test lint before submitting a PR
• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Release Notes

NONE

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign piyush-garg after the PR has been reviewed.
You can assign the PR to them by writing /assign @piyush-garg in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ab-ghosh]

Upgrade test results:

Before the upgrade

After the upgrade

Updating the TektonConfig with the scheduler configuration (multi-cluster-disabled: false and multi-cluster-role: Hub) Result's watcher and Retention Policy Agent being scaled down to 0.