What if I've already published a Community Operator?
This section will outline the steps required to publish your OperatorHub.io or OpenShift Community Operator to the Red Hat Certified catalog listing in OpenShift OperatorHub.
The following changes must be made to the operator as well as the operator metadata (CSV) prior to submission (each item is covered in depth further below):
- The operator must consume the certified application image(s) aka operands from RHCC.
- The service account of your operand, (eg: the service account used to run your application's pods) must have the proper Security Context Constraint (SCC) applied in order to run containers either as root or a specific UID in OpenShift. This applies specifically to OperatorHub.io/Vanilla K8s operators
- Set the
packageNameof the metadata bundle in
package.yamlmust be distinct from that of your community operator.
- The metadata bundle must be flattened and contain no sub-directories or extraneous files