cert-manager: error: no kind "ClusterIssuer" is registered for version "certmanager.k8s.io/v1alpha1
/kind bug
What happened:
After creating ClusterIssuer, looking at the logs shows:
error: no kind “ClusterIssuer” is registered for version “certmanager.k8s.io/v1alpha1”
Environment:
- Kubernetes version (use
kubectl version): 1.9.2 - Cloud provider or hardware configuration**: Azure AKS
- Install tools: cert-manager-v0.3.1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 10
- Comments: 20 (3 by maintainers)
certmananger -> certmanager?
@markhorrocks did you try
apiVersion: cert-manager.io/v1alpha2?Same issue, reading this post, I figured
certmanager.k8s.io/v1alpha1 -> cert-manager.io/v1alpha2andhttps://acme-staging.api.letsencrypt.org/directory -> https://acme-staging-v02.api.letsencrypt.org/directorythank you
more details here: https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/
now… I am getting this validation error
removed the http01, seems to work but not sure about the consequences. Getting off topic. I will stop here.
update: found the solution here https://cert-manager.io/docs/configuration/acme/
@nicolls1 @sneko @ivalexa I have had this issue as well with the letsencrypt-staging issuer. The fix was to update the ACME server URL in your issuer:
https://acme-staging-v02.api.letsencrypt.org/directoryinstead ofhttps://acme-staging.api.letsencrypt.org/directoryHi there, I’ve been facing the same problem here, have tried to change the url but it had no effect in my scenario:
I’m trying to follow the steps in this tutorial, but I’m still getting the message:
Any of u had a different outcome?
How could I install the resource certmanager.k8s.io/v1alpha1 without using Helm?
It sounds like you’ve not properly installed the CRDs for cert-manager. How did you install it? via Helm?
This worked cert-manager v0.11.0
@duzy please keep issues on topic; but to answer your question, see “static manifests” in https://cert-manager.readthedocs.io/en/latest/getting-started/2-installing.html
Thanks @KimGressens ! It solves the error message I had.
Note that for prod Issuer you need to specify: https://acme-v02.api.letsencrypt.org/directory