Epic Goal

• Drive the performance work regarding GRC and RBAC

Why is this important?

 * With RBAC we were looking at the recommendation of using policy to manage the rolebindings on the managed clusters, e.g. new app deployed and we need to appropriate rolebindings to that namespace.   With this approach, we know the fine grained access control on the hub cluster and can manage it.  After talking to customers we learned that they range from 300 up to 5000 apps.  This raised a concern on the amount of overhead ACM would add on the managed cluster in order to deploy/ensure compliance with these policies.   Unfort, our tests are proving that the overhead of using policy is too high at this moment.  Thus, we need to make improvements to lower the overall impact on the managed cluster.

Scenarios

1. Switch away from Polling, adding concurrency, adding a metric if Controller is overloaded

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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>