-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support latest cert-manager operator for openshift #39
Comments
I think openshift-routes will work with fine with cert-manager > v1.8.0, but it won't necessarily support new features or APIs added in newer versions of cert-manager. There are a couple PRs in progress that do upgrade the CMAPI used in openshift routes to use v1.12.X #29 #28 I would agree it would be very nice to have this packaged in a helm chart and/or OLM so end users can use these familiar tools as a mechanism to install, upgrade, and manage dependencies since there are multiple operators involved and as you mentioned may come from different sources. Installing via OperatorHub is common for OpenShift users as it's integrated directly in the console and OLM is available by default. I think after this point though it would probably be the responsibility of Red Hat to bundle in openshift-routes as a separate controller inside their OLM packaged cert-manager, or include it has a separate OLM dependency if openshift-routes were packaged separately. |
@ctrought Thanks you ! |
@ctrought Agreed, a Helm chart and an OLM package would be great. I don't think the static manifest doesn't match what folks on OpenShift expect. I'd love to see Red Hat help in bundling openshift-routes! 😇 |
We now have a Helm chart and test openshift-routes with the latest version of cert-manager! |
Currently the openshift-routes depends on cert-manager v1.8.0. However the latest OCP 4 has cert-manager v1.11.4.
It should be updated to be align with openshift. And it should be bundled with each openshift versions.
Users should be able to install a matching version of openshift route from operator-hub.
The text was updated successfully, but these errors were encountered: