CODEWITHSUNDEEP
kubernetesdigital-oceanlets-encryptnginx-ingresscert-manager
agusgambina
agusgambina

Reputation: 6699

Digital Ocean Kubernetes Let's Encrypt Waiting for HTTP-01 challenge propagation: failed to perform self check

I have been trying to deploy a Kubernetes cluster in Digital Ocean. Everything seems to work except when I try to apply the tls certificates. I have been following these steps, but with Nginx Ingress Controller v1.0.0 and cert-manager v1.5.0.

I have two urls, let's say api.example.com and www.example.com

Checking the challenge I saw Waiting for HTTP-01 challenge propagation: failed to perform self check GET request...

I tried adding the following annotations to the ingress:

kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: "letsencrypt-prod"

Or using this service as a workaround:

kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx
  namespace: ingress-nginx
  annotations:
    service.beta.kubernetes.io/do-loadbalancer-enable-proxy-protocol: "true"
    service.beta.kubernetes.io/do-loadbalancer-hostname: "www.example.com"
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  #CHANGE/ADD THIS
  externalTrafficPolicy: Cluster
  type: LoadBalancer
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
  ports:
    - name: http
      port: 80
      targetPort: http
    - name: https
      port: 443
      targetPort: https

If I go to the URL challenge I am able to see the hash, but I am stuck, I am not sure why it is failing or the steps to solve this.

Upvotes: 1

Views: 1353

Answers (1)

Mikołaj Głodziak
Mikołaj Głodziak

Reputation: 5277

As agusgambina has mentioned in the comment, problem is solved:

I was able to make this work, first I need to get the load balancer id executing k describe svc ingress-nginx-controller --namespace=ingress-nginx and then pasting in the annotation kubernetes.digitalocean.com/load-balancer-id: “xxxx-xxxx-xxxx-xxxx-xxxxx” thanks for your comments, it helped me to solve the issue.

This problem described also here and there is also a tutorial
How to Set Up an Nginx Ingress with Cert-Manager on DigitalOcean Kubernetes.

Upvotes: 2

Related Questions