Background:

• Customers getting comfortable using GitOps and adding more and more load to their Argo CD instances, large customers want to migrate their (many and sizeable) existing applications to OpenShift GitOps
• Both the OpenShift GitOps operator and a single instance of Argo CD are having their scaling limits reported by customers pushing the boundaries of what can be done today 

Objective:

• The majority of our customers can comfortable scale their Argo CD instances without running into limitations of the product itself

Timeline

• Q2 for operator work and getting proposals into the upstream
• Q3 for upstream progress on proposals

Dependencies

Upstream reviewers for Argo CD proposals and code changes

Customer Need

Customers requesting single-instance scaling improvements:

• Verizon
• BBVA
• VodaphoneZiggo
• Proximus
• Intesa
• Publix

Success Criteria

• Operator scalability (within a cluster) improves
• Argo CD single instance vertical scalability improves

Expected Results (what, how, when)

• CR counts for applications continue to increase
• Fewer customers report scalability limitations in the operator or in Argo CD 

Metrics

• Existing operator benchmarks are improved
• Argo CD controller scalability benchmarks are improved
• Operator usage data from Tableau / Thanos 

Post Completion Review – Actual Results

TBD