Feature Overview (aka. Goal Summary)  

Users can specify the namespaces in which an operator/extension operates.

Goals (aka. expected user outcomes)

When installing an operator/extension using OLM, users need an option to specify the namespaces in which it should operate. **

Without this functionality:

• Existing operators/extensions built to work with OLM v0 and the registry+v1 format requiring this are unusable
• Users installing operators/extensions can not limit the scope in which an operator/extension operates, restricting the ability to adhere to the Principle of Least Privilege

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

• When installing an operator/extension, the namespaces that an operator/extension may watch can be specified
• If namespaces are specified and the operator/extension does not support a mode in which a limited set of namespaces can be watched, the installation fails

• There is a documented standard for how OLM tells an operator/extension which namespaces to watch

• An operator/extension has a way to opt-in and signal their support for this functionality
• When an opted-in operator/extension’s configuration is modified and namespaces are added/removed to the watch list, the operator/extension updates accordingly

• For operators/extensions built with the registry+v1 bundle format, specifying support for the MultiNamespace InstallMode is interpreted as opting into this functionality

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Upstream engineering brief: https://docs.google.com/document/d/1EGcJUjEqyA6CVfRHP5EFzdAJZ8EZAv5oBU5wTJfjhso/edit?usp=sharing

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>