You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Versions of relevant software used
I'm using master branch of Git as of today
What happened
Install instructions didn't work
What you expected to happen
Install instructions to work
How to reproduce it (as minimally and precisely as possible):
Install latest version of Cert-Manager and follow install instructions
Full logs to relevant components
unable to recognize ".": no matches for kind "Certificate" in version "cert-manager.io/v1alpha2"
unable to recognize ".": no matches for kind "Issuer" in version "cert-manager.io/v1alpha2"
Anything else we need to know
I'm new to Kustomize but used K8s, Kubectl and Helm a bunch. My cluster is running the latest Helm deploy of cert-manager 1.6.1 which uses a CRD of certificates.k8s.io/v1. I tried to run without cert maanger and I couldn't get pods to start. I'm in EKS. I was try to run to test env/sandbox fwiw.
The text was updated successfully, but these errors were encountered:
Versions of relevant software used
I'm using master branch of Git as of today
What happened
Install instructions didn't work
What you expected to happen
Install instructions to work
How to reproduce it (as minimally and precisely as possible):
Install latest version of Cert-Manager and follow install instructions
Full logs to relevant components
unable to recognize ".": no matches for kind "Certificate" in version "cert-manager.io/v1alpha2"
unable to recognize ".": no matches for kind "Issuer" in version "cert-manager.io/v1alpha2"
Anything else we need to know
I'm new to Kustomize but used K8s, Kubectl and Helm a bunch. My cluster is running the latest Helm deploy of cert-manager 1.6.1 which uses a CRD of
certificates.k8s.io/v1
. I tried to run without cert maanger and I couldn't get pods to start. I'm in EKS. I was try to run to test env/sandbox fwiw.The text was updated successfully, but these errors were encountered: