Operator release

Operator release workflow

Release workflow contains all jobs. This can be found in action tab of the project.

When operator is merged to master following scenarios will happen:

For a k8s case (upstream-community-operators)

1. Push to quay (to support old app registry)
2. Build index image for k8s
3. Build image image for operatorhub.io page
4. Deploy operatorhub.io page

For an Openshift case (community-operators)

1. Push to quay (to support old app registry)
2. Build index image for different Openshift versions (v4.6 and v4.7 in this case) and multiarch image is also is produced.
3. Build image image for dev.operatorhub.io page (for development purposes only)
4. Deploy dev.operatorhub.io page (for development purposes only)

Operator is published

After this process, your operator will be published.

Index image location

For Openshift:

registry.redhat.io/redhat/community-operator-index:v4.6 registry.redhat.io/redhat/community-operator-index:v4.7 registry.redhat.io/redhat/community-operator-index:latest - this is a clone of v4.6 from historical reasons as it always was a clone of v4.6. Will be deprecated in the future.

For Kubernetes:

quay.io/operatorhubio/catalog:latest

Bundle images location

For Openshift:

quay.io/openshift-community-operators/

For Kubernetes:

quay.io/operatorhubio/