Epic Goal

• Package the operator for OLM and make it available for consumption in the RH Operators Catalog and the Operatorhub.

Why is this important?

• KBS is critical component for Confidential Containers (CoCo) and customers need the ability to deploy it on their clusters.

User Stories

• As a cluster-admin I wish to install the KBS operator in my cluster.
• As a cluster-admin I wish to uninstall the KBS operator from my cluster without side-effects (e.g., dangling resources, namespaces,...).
• As a cluster-admin I would like the operator I deploy on my cluster to be compliant with company standards and best-practices.
• As a cluster-admin I want to have all the KBS operator dependencies automatically installed.

Requirements

• Meet OLM Operator requirements in [1].
• The Operator MUST be
  • packaged for OLM.
  • validated.
  • Installable via OLM.
  • Upgradable
  • Uninstallable via OLM.
• All the Operator Dependencies MUST be handled.
• The Operator MUST be available in the RH Operator Catalog [2][3].
• The Operator COULD be available for consumption on the Operatorhub.

References

1. https://docs.engineering.redhat.com/display/CFC/Best_Practices
2. https://catalog.redhat.com/software/operators/search?p=1&vendor_name=Red [ Hat%2C Inc|https://catalog.redhat.com/software/operators/search?p=1&vendor_name=Red%20Hat%2C%20Inc].
3. https://comet.engineering.redhat.com/containers/products