CODEWITHSUNDEEP
kubernetesdigital-oceanlets-encryptkubectl
markhorrocks
markhorrocks

Reputation: 1518

No matches for kind ClusterIssuer on a Digital Ocean Kubernetes Cluster

I have been following this guide to create an nginx-ingress which works fine.

Next I want to create a ClusterIssuer object called letsencrypt-staging, and use the Let's Encrypt staging server but get this error.

kubectl create -f staging_issuer.yaml

error: unable to recognize "staging_issuer.yaml": no matches for kind "ClusterIssuer" in version "certmanager.k8s.io/v1alpha1"

I have searched for solutions but can't find anything that works for me or that I can understand. What I found is mostly bug reports.

Here is my yaml file I used to create the ClusterIssuer.

apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
 name: letsencrypt-staging
spec:
 acme:
   # The ACME server URL
   server: https://acme-staging-v02.api.letsencrypt.org/directory
   # Email address used for ACME registration
   email: your_email_address_here
   # Name of a secret used to store the ACME account private key
   privateKeySecretRef:
     name: letsencrypt-staging
   # Enable the HTTP-01 challenge provider
   http01: {}

Upvotes: 2

Views: 4067

Answers (3)

Tushar Mahajan
Tushar Mahajan

Reputation: 2160

Try following this link, the cert-manager LetsEncrypt has notified that it will be blocking all traffic for versions < 0.8.0, Hence you can use Jetstack's installation steps, and then you can follow

this link to get TLS certificates creation, It has worked for me.

Let me know, if you face issues

Upvotes: 1

Daniel Ospitia
Daniel Ospitia

Reputation: 1

Sometimes is the space character used in the .yaml file. Ensure that you are not using tabs instead of spaces. You can delete the line in the "Kind" (or any that is showing error) and write again using space bar to separate, not tabs.

Upvotes: 0

markhorrocks
markhorrocks

Reputation: 1518

I fixed the problem by running helm del --purge cert-manager

and then 

helm install --name cert-manager --namespace kube-system stable/cert-manager --set createCustomResource=true

Upvotes: 1

Related Questions