-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release on OperatorHub #21
Comments
Hey @LorbusChris thanks for raising this issue and apologies for the slow response. If you have time, please review #26 where I'm attempting to package cert-manager for OperatorHub, targeting both Kubernetes and OpenShift |
Looks like I'm a bit late to the party :) Thanks for seeing this through @wallrj! |
Hey @LorbusChris . We merged it, but there's still quite a lot of work to do. I want to get all the CRDs properly documented on https://operatorhub.io/operator/cert-manager That's how it seems to work in the OperatorHub web console on OpenShift . |
Right, such a default would make sense to me. Would you mind filing an issue on https://github.com/operator-framework/community-operators/issues? |
I came across https://cert-manager.io/docs/installation/openshift/#installing-with-cert-manager-operator which links to a non-existent page. So I searched and found this repo :)
It seems the operator isn't yet available on OperatorHub (a now very outdated version was added to the
dev
branch last year: https://github.com/operator-framework/community-operators/tree/dev/upstream-community-operators/cert-manager).Since this repo also hasn't been updated in a while, I'm wondering whether there still is a plan to release on OperatorHub at all?
In the OperatorHub Registry repo (https://github.com/operator-framework/community-operators) there are two catalogs:
community-operators
for OpenShift (and its community variant OKD), as well asupstream-community-operators
for upstream Kubernetes.It would be great if this operator could be added to both of these :) I'm happy to help with it, too!
The text was updated successfully, but these errors were encountered: