Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Currently, OLMv1 lacks a native configuration mechanism comparable to widely-adopted solutions such as Helm's values files or the SubscriptionConfig of OLMv0. Users are forced to rely on external configurations or bespoke operator logic, complicating deployments and limiting adaptability. A built-in configuration system addresses this gap, simplifying operator deployment and enabling more precise, consistent resource management. This feature aims to introduce a standardized, declarative mechanism for configuring packages installed via OLMv1 through the ClusterExtension API.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

The primary goal is to empower users to configure the packages they install through OLMv1 by introducing a native, declarative configuration interface in the ClusterExtension API. This will ensure:

• Enhanced Flexibility: Operators can be deployed and customized to fit diverse environmental and application requirements.
• Declarative Control: Configuration is managed as part of the ClusterExtension object, supporting GitOps workflows and consistent state management.
• Alignment with Best Practices: Bridging the gap with configuration paradigms found in Helm and the SubscriptionConfig of OLMv0.

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.

<enter general Feature acceptance here>

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.

• Helm charts, and specifically supporting a native analogue of Helm values.yaml files, is out of scope for this feature. Potential support of this will be addressed in 

   

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Operators, designed to manage complex applications on Kubernetes, often require specific configurations beyond a basic installation. In the current OLMv1 (Technology Preview) framework, as represented by the ClusterExtension API, there isn't a direct and standardized mechanism for users to pass custom configuration parameters to the installed packages. This limitation forces users to employ external configuration methods or rely on custom operator logic, reducing flexibility and hindering streamlined, GitOps-friendly deployments. This contrasts with established patterns like Helm-based charts, which readily accept values files for configuration, and the existing SubscriptionConfig capability in OLMv0. This feature aims to allow users to configure packages installed via OLMv1 using a native, declarative configuration interface in the ClusterExtension API.

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>