Epic Goal

• Explore and implement various ways to improve OpenShift GitOps performance at scale

Why is this important?

• Several customers are complaining about OpenShift GitOps performances especially when it is managing several namespaces

Scenarios

1. Cluster cache is optimized to only cache resources/APIs in use and not the whole cluster
2.  Reduced the number of k8s watches to the bare minimum that Argo CD requires 
3. cache and watches need to have an expiration policy and must be setup and tear down based on usage

Acceptance Criteria (Mandatory)

• As a user of OpenShift GitOps in cluster scoped mode, I want to manage multiple clusters with my Argo CD instance without worrying too much about resource consumption
• As a user of OpenShift GitOps in namespace scoped mode, I want to be able to manage more than a couple of namespaces without running into performance issues

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment