Value Statement

Advanced Cluster Management is following the control plane lead, for our management control plane. This will make OOM's less likely and put the fix in the customers hand. This requires that valid sizing for resources physical and virtual hardware are published and dashboards / instructions exist on how to monitor and adjust resources (management control plane - Infrastructure nodes).

Similar to the work done in ACM-16344 for CAPI controllers and ACM-26273 for multicluster-role-assignment, the cluster-permission controller needs to have resource limits removed to align with the control plane approach for the management control plane.

Repository: https://github.com/stolostron/cluster-permission

Definition of Done for Engineering Story Owner (Checklist)

• All hub deployments for the cluster-permission controller are launched with NO Limits for Memory & CPU

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

[ ] ACM full regression QE is aware of this change

Support Readiness

[ ] The must-gather script has been updated.

Documentation Readiness

[ ] I have provided sizing (how much CPU & Memory resources my component requires.
• Minimum
• For different number of my component resources
• 25, 100, 1000, 3500 clusters
• ClusterPermission resources at scale
• MulticlusterRoleAssignments at scale