Epic Goal

A ScopedCache library that operator authors can use to work with rbac scoping scenarios.

Why is this important?

OLM is moving towards a descoped operator model. Operators will be installed as singletons and cluster scoped. There will be a scoped templating operator (oria-operator) that allows cluster admins to determine the rbac for an operator in their cluster. Sometimes the rbac can change in the operator's lifecycle from no access during the installation phase to having specific access to one namespace then to a different one during it's running phase. This scopedcache will allow the operator to handle such rbac changes.

Scenarios

1. TBD

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. oria-operator is downstream (OSDK-1900)

Previous Work (Optional):

1. …

Open questions::

1. Do we need phases for this epic?

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>