List the Operator in OperatorHub.io
Summary
Publish the Operator Lifecycle Manager bundle
to OperatorHub.io
Details
Once #226 (closed) has been completed, publish the resulting OLM bundle via OperatorHub.io according to their requirements, and in accordance with the patterns of the Operator-SDK.
Requirements
k8s 1.22
kubernetes 1.22 compliance is required, which is targeted by gitlab-org&6883 (closed)
IMPORTANT Kubernetes has been deprecating API(s) which will be removed and no longer available in 1.22 and in the Openshift version 4.9. Note that your project will be unable to use them on OCP 4.9/K8s 1.22 and then, it is strongly recommended to check Deprecated API Migration Guide from v1.22 and ensure that your projects have them migrated and are not using any deprecated API.
process compliance
To do this, we follow contributing prerequisities which includes a Developer Certificate of Origin Signed-off-by
trailer.
Because the repository feeding OperatorHub also feeds OpenShift's internal OperatorHub (upstream-community-operators
for Kubernetes.
If your Operator works on both Kubernetes and OpenShift, place a copy of your packaged bundle in theupstream-community-operators
directory, as well as thecommunity-operators
directory. Submit them as separate PRs.
Current Guidance on contribution is that:
- OperatorHub.io submissions should go to https://github.com/k8s-operatorhub/community-operators/tree/main/operators
- Embedded OperatorHub in OpenShift and OKD submissions should go to https://github.com/redhat-openshift-ecosystem/community-operators-prod/tree/main/operators
These MRs are raised to https://github.com/operator-framework/community-operators
. We must also configure the appropriate patterns for CI within that project