Setting up HPA for Tekton Services

I wanted to setup HPA for Tekton and it's related services (including tekon-pipelines, workloads and resolvers), however, in the repo - I only see reference for webhook-hpa.

https://github.com/tektoncd/pipeline/blob/main/config/webhook-hpa.yaml

Questions -

• Is there any reason for not having hpa for others?
• If we add multiple replica for tekton-event-controller, will end up redundant events?
• Any recommendation on best practices on HPA for tekton?
• For tekton-events-controller specifically: How does it handle event deduplication across replicas?
• Is there built-in coordination between multiple event controller instances?
• Are there any known issues or considerations when scaling tekton-controller beyond a single replica?
• What's the recommended approach for handling leader election in multi-replica tekton-controller deployments
• Are there any shared resources or locks that could cause conflicts with multiple controller replicas?

cc @tektoncd/operator-maintainers

Start with config/webhook-hpa.yaml and compare its HPA setup with the Tekton services named in the issue. Investigate replica behavior, event deduplication, leader election, and shared resources before proposing an approach. Done means the scaling recommendation and implementation scope are agreed and documented.