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
no matches for kind "ClusterIssuer" in version "cert-manager.io/v1" #3246
Comments
I am also getting this error when upgrading to v1.0.0 |
Can you get us the output of |
attached.. |
@RobbieJVMW we haven't finished updating the installation instructions for OpenShift. See cert-manager/website#318 Is it possible that you've actually installed cert-manager 0.16.1? That previous version does not support the new V1 API. |
Sounds entirely possible - the install guide did point at a 0.16.1 .. look's like the doc has been updated. I will re-test. |
yes, the new doc's pointing at the 1.0 release has resolved the issue. |
Robbie please share the updated doc link, you have used to resolve this. |
The install guide on on cert-manager.io has been updated to link to the v1.0 deployment yaml. I didn’t need to do anything apart from re-test using the new config. |
This ClusterIssuer still does not working when following steps found here: Kube version: 1.18 Error Response back: |
@vosuyak what do you see for |
@vosuyak Had the same problem but found out that in the newer versions when using HELM the cluster CRDs are not installed by default. It worked after uninstalling an reinstalling with:
note the --set installCRDs=true at the end. Hope this helps. |
@proligde I'm still running into this issue on a fresh install with helm 3.3.4 using cert-manager as a dependency: e.g.
From what I've read, the problem sounds like the discovery caching logic in helm3. So you can't both install CRDs and use them in a single helm install step, if installing CRDs through an ordinary template, like cert-manager does. The recommended way of installing CRDs in helm3 is putting them in the Right now the workaround is to install my project in two separate commands - one to installCRDs for cert-manager, the other to set up my project and reference these CRDs, which is a little annoying. |
@jnu cert-manager as a chart dependancy will always give issues due to the Helm dependancy model. |
This was my issue. Thanks! |
The version for cert-manager in this examples returns '**no matches for kind "ClusterIssuer" in version "cert-manager.io/v1"**' (cert-manager/cert-manager#3246) The latest ( or v1.0.1+) version works correctly and the install guide on on cert-manager.io has been updated to link to the v1.0 deployment yaml. I didn’t need to do anything apart from re-test using the new config (https://cert-manager.io/docs/configuration/acme/http01/).
this fixed it for me, deleting the cert-manager and reinstalling it using the |
@jnu did you find a workaround? I'm still hitting this exact same issue. |
Setting |
in this case, why not add a |
I'm having the same issue and flux keeps failing to upgrade the chart :
I'm upgrading from 0.13.0 > 1.11.1 I tried removing the CRDs before the upgrade 0.13.1 and tried installing the new CRDs but it still fails |
Describe the bug:
Following the installation instructions for OpenShift (https://cert-manager.io/docs/installation/openshift/#login-to-your-openshift-cluster). The deployment completes successfully however
kind:ClusterIssuer
is not recognised.Expected behaviour:
kind: ClusterIssuer
recognised in the yaml.Steps to reproduce the bug:
Using OpenShift 4.5.7 follow installation instructions (Option 1).
Environment details::
/kind bug
The text was updated successfully, but these errors were encountered: