Epic Goal

Reduce the size of the MCE operator's cache memory requirements when running in large clusters.

Why is this important?

In order to support high scale the MCE installer needs to run reliably and without risk of exceeding memory limits. 

Scenarios

• User is managing thousands of clusters
• User is running MCE on a large cluster with many other applications

Acceptance Criteria

• MCE runs in a cluster managing 3000+ SNOs
• As number of resources (namespaces, secrets, managedClusters, etc.) grows, the memory usage of the MCE operator pod does not grow linearly

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. Added option to skip caching certain resources with a flag https://github.com/stolostron/backplane-operator/pull/375

Open questions:

1. Can we test the memory requirements without needing to run in a scaled environment?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>