<p>I'm trying to use cert-manager to issue a certificate via LetsEncrypt.</p>

<p>I've followed through with the steps here <a href="http://docs.cert-manager.io/en/latest/getting-started/index.html" rel="noreferrer">http://docs.cert-manager.io/en/latest/getting-started/index.html</a></p>

<p>However, my existing ingress is not being modified (I assume it needs to modify it due to adding a path for <code>.well-known/...</code>. </p>

<p>Instead I see an ingress created for this with a name like: <code>cm-acme-http-solver-kgpz6</code>? Which is rather confusing?</p>

<p>If I get the yaml for that ingress I see the following for rules:</p>

<pre><code>spec:
  rules:
  - host: example.com
    http:
      paths:
      - backend:
          serviceName: cm-acme-http-solver-2dd97
          servicePort: 8089
        path: /.well-known/acme-challenge/2T2D_XK1-zIJJ9_f2ANlwR-AcNTm3-WenOExNpmUytY
</code></pre>

<p>How exactly is this meant to work? As the documentation seems rather sparse.</p>

<p>The record you are seeing is for the challenge. It needs to succeed to configure the cert. If you are using "example.com" as the domain then it will not succeed. To get this to work you'll need to configure a DNS record for a valid hostname so that LetsEncrypt can resolve the domain and complete the check. </p>

<p>Usually you will not even see the challenge ingress resource. It usually runs the challenge and then removes itself as long as DNS and the hostname have been configured correctly. After it is removed the resource you created will get loaded into your ingress controller.  </p>

<p>There are a few ingress controllers that do not support multiple ingress resources per hostname. They will load one ingress resource and ignore the other, so this is sort of a workaround/fix to the issue.</p>
