Feature Overview (aka. Goal Summary)  

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

• RHDE users want to be able to install operands into MicroShift clusters as part of building their system images, without running the operator or OLM on the cluster.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

• A user can add information to their image blueprint to cause an operand from an operator in an OLM catalog to be installed into the RHDE image with the container images added to the CRI-O cache and the manifests to load the operand added to a location where MicroShift can pick them up automatically.

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.

Phase I: A user can run a tool themselves, or in a build pipeline, to query an OLM instance and extract the manifests and image references to use for the operands of a specific operator and receive TOML output suitable for adding to an Image Builder blueprint when building their RHDE image.

Phase II: A user can add an OLM instance as a "source" to Image Builder and specify that the operands for an operator should be added to their image, similar to how they add RPMs to the image today (minimal details, version specification, etc.). The end result should be the same, the manifests and container images are added to the RHDE image.

Use Cases (Optional):

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

OEM partners building platforms on RHDE and end users deploying applications on RHDE want to be able to use specific operators on MicroShift, without deploying the operator or OLM.

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.

Out of Scope

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

Background

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

Customer Considerations

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

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects 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.