Story (Required)

As a support engineer, I want to distribute the destination clusters managed by an ArgoCD instance evenly across the different application controller instances that is running.

The goal of this story is document how to use the round-robin algorthim of distributing clusters equally across the available shards.

Background (Required)

Currently, users can spread the clusters equally across the different shards ( application controller) instances as the cluster load is spread using a random hash. This can create hotspots where one instance can get severly loaded, whereas others remain in less load or even be idling. Such a situtaion may not be desirable, as there is considerable resource consumed for maintaining the cache even by instances that are idling. Users can now select a different algorithm to distribute the load more evenly across the different instances.

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-407

Acceptance Criteria (Mandatory)

• Documentation added to Confluence on how to use the the round-robin algorithm in upstream ArgoCD 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