Feature Overview (aka. Goal Summary)  

MicroShift users want to be able to install selected operators into MicroShift clusters.

Goals (aka. expected user outcomes)

Provide tooling so that a user can add information to their image blueprint  or rpm installation to add an operator from an OLM catalog to be installed into MicroShift. Provide meta-data to indicate which operators are supported on MicroShift.

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.

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 a specific operator. These artefacts can be integrated by the user into their ostree toml file or other ways of deployment theyuse.

An operator provider can declare via meta-data that an operator is fully supported on MicroShift.

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 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.

1. MicroShift supports only the standard k8s API, next to no OpenShift specific APIs. Can we develop a tooling that analyses based on the existing meta-data of an operator that it can run on MicroShift?
2. Where is the OLM catalog the tooling extract the necessary artefacts running? Can it / has to be a OCP instance from the user? Can it be opertorhub.io or something similiar?

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.