Story (Required)

As a support engineer, I want to enable auto scaling of application controllers of ArgoCD based on the number of destination clusters that are managed by that ArgoCD instance.

The goal of this story is document how to use the autoscaling feature in GitOps Operator

Background (Required)

Currently, users have to scale the number of application controller instances required to manage different destination clusters by editng the spec.applicationController.replicas value in the ArgoCD. The newly developed auto-scaling feature in Openshift GitOps operator, helps to reduce this manual effort by automatically increasing/decreasing the replica count based on the number of clusters it manages and how many clusters are being managed per replica.

Out of scope

<Defines what is not included in this story>

Approach (Required)

Provide documentation how to use the must-gather for both, CEE and our customers. 

Dependencies

1. GITOPSRVCE-409

Acceptance Criteria (Mandatory)

• Documentation added to Confluence on how to use the the auto scaling feature for both, CEE and our customers
• A blog on the subject

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met