Epic Goal

Today controller-runtime has support for multinamespace cache and for selecting resources using a selector. What's needed now is to have a more dynamic multinamespace cache and the ability to have delayed permissions, i.e. being granted permissions after the cache is normally initialized.

Why is this important?

There is a proposal to descope operators and make them cluster scoped. There were some concerns with this move for those operators using controller-runtime since they will need to access both cluster and namespaced resources. Today controller-runtime has support for multinamespace cache and for selecting resources using a selector. What's needed now is to have a more dynamic multinamespace cache and the ability to have delayed permissions, i.e. being granted permissions after the cache is normally initialized.

Acceptance Criteria

• Complete an enhancement proposal in upstream controller-runtime
• Submit an implementation of the above proposal

Engineering Notes

These are all of the notes regarding descoping and the dynamic multinamespace cache.

• Doc
• Slack Discussion
• Office Hour Discussion 4/15
• Slack private Chat

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 docum