<p>At <a href="https://docs.cert-manager.io/en/latest/tutorials/acme/quick-start/index.html#" rel="nofollow noreferrer">step 3</a> I got the IP address as follow. And I customized my DNS according to this <a href="https://medium.com/@ayyazzafar/how-to-install-letsencrypt-ssl-certificate-using-cert-manager-on-google-kubernetes-engine-gke-4553889688bc" rel="nofollow noreferrer">article</a></p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get svc
NAME                                       TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)                      AGE
kubernetes                                 ClusterIP      10.51.240.1     &lt;none&gt;         443/TCP                      10d
quickstart-nginx-ingress-controller        LoadBalancer   10.51.251.156   35.247.160.2   80:30686/TCP,443:32595/TCP   87s
quickstart-nginx-ingress-default-backend   ClusterIP      10.51.253.66    &lt;none&gt;         80/TCP                       86s
</code></pre>
<blockquote>
<p>The external IP that is allocated to the ingress-controller is the IP to which all incoming traffic should be routed. To enable this, add it to a DNS zone you control, for example as example.your-domain.com.</p>
<p>This quickstart assumes you know how to assign a DNS entry to an IP address and will do so.</p>
</blockquote>
<p><code>DNS zone</code>
<a href="https://i.stack.imgur.com/nHzXv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/nHzXv.png" alt="enter image description here" /></a></p>
<p><code>domains.google.com</code>
<a href="https://i.stack.imgur.com/9Xt7I.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/9Xt7I.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/PDpOR.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/PDpOR.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/SEZxV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SEZxV.png" alt="enter image description here" /></a></p>
<p>I can <code>$ curl -kivL -H 'Host: singh.hbot.dev' 'http://singh.hbot.dev'</code>
Here is the output of <code>kuard</code></p>
<pre class="lang-sh prettyprint-override"><code>* Rebuilt URL to: http://singh.hbot.dev/
*   Trying 35.247.160.2...
* TCP_NODELAY set
* Connected to singh.hbot.dev (35.247.160.2) port 80 (#0)
&gt; GET / HTTP/1.1
&gt; Host: singh.hbot.dev
&gt; User-Agent: curl/7.54.0
&gt; Accept: */*
&gt;
&lt; HTTP/1.1 308 Permanent Redirect
HTTP/1.1 308 Permanent Redirect
&lt; Server: nginx/1.15.8
Server: nginx/1.15.8
&lt; Date: Thu, 14 Mar 2019 08:59:24 GMT
Date: Thu, 14 Mar 2019 08:59:24 GMT
&lt; Content-Type: text/html
Content-Type: text/html
&lt; Content-Length: 171
Content-Length: 171
&lt; Connection: keep-alive
Connection: keep-alive
&lt; Location: https://singh.hbot.dev/
Location: https://singh.hbot.dev/

&lt;
* Ignoring the response-body
* Connection #0 to host singh.hbot.dev left intact
* Issue another request to this URL: 'https://singh.hbot.dev/'
*   Trying 35.247.160.2...
* TCP_NODELAY set
* Connected to singh.hbot.dev (35.247.160.2) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  start date: Mar 14 08:22:58 2019 GMT
*  expire date: Mar 13 08:22:58 2020 GMT
*  issuer: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fdf3000e200)
&gt; GET / HTTP/2
&gt; Host: singh.hbot.dev
&gt; User-Agent: curl/7.54.0
&gt; Accept: */*
&gt;
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
&lt; HTTP/2 200
HTTP/2 200
&lt; server: nginx/1.15.8
server: nginx/1.15.8
&lt; date: Thu, 14 Mar 2019 08:59:24 GMT
date: Thu, 14 Mar 2019 08:59:24 GMT
&lt; content-type: text/html
content-type: text/html
&lt; content-length: 1689
content-length: 1689
&lt; vary: Accept-Encoding
vary: Accept-Encoding
&lt; strict-transport-security: max-age=15724800; includeSubDomains
strict-transport-security: max-age=15724800; includeSubDomains

&lt;
&lt;!doctype html&gt;

&lt;html lang=&quot;en&quot;&gt;
&lt;head&gt;
  &lt;meta charset=&quot;utf-8&quot;&gt;

  &lt;title&gt;KUAR Demo&lt;/title&gt;

  &lt;link rel=&quot;stylesheet&quot; href=&quot;/static/css/bootstrap.min.css&quot;&gt;
  &lt;link rel=&quot;stylesheet&quot; href=&quot;/static/css/styles.css&quot;&gt;

  &lt;script&gt;
var pageContext = {&quot;hostname&quot;:&quot;kuard-79b5d46779-5slz8&quot;,&quot;addrs&quot;:[&quot;10.48.2.20&quot;],&quot;version&quot;:&quot;v0.8.1-1&quot;,&quot;versionColor&quot;:&quot;hsl(18,100%,50%)&quot;,&quot;requestDump&quot;:&quot;GET / HTTP/1.1\r\nHost: singh.hbot.dev\r\nAccept: */*\r\nUser-Agent: curl/7.54.0\r\nX-Forwarded-For: 10.148.0.49\r\nX-Forwarded-Host: singh.hbot.dev\r\nX-Forwarded-Port: 443\r\nX-Forwarded-Proto: https\r\nX-Original-Uri: /\r\nX-Real-Ip: 10.148.0.49\r\nX-Request-Id: ba73c8e44498c36480ea0d4164279561\r\nX-Scheme: https&quot;,&quot;requestProto&quot;:&quot;HTTP/1.1&quot;,&quot;requestAddr&quot;:&quot;10.48.2.18:41748&quot;}
  &lt;/script&gt;
&lt;/head&gt;


&lt;svg style=&quot;position: absolute; width: 0; height: 0; overflow: hidden;&quot; version=&quot;1.1&quot; xmlns=&quot;http://www.w3.org/2000/svg&quot; xmlns:xlink=&quot;http://www.w3.org/1999/xlink&quot;&gt;
&lt;defs&gt;
&lt;symbol id=&quot;icon-power&quot; viewBox=&quot;0 0 32 32&quot;&gt;
&lt;title&gt;power&lt;/title&gt;
&lt;path class=&quot;path1&quot; d=&quot;M12 0l-12 16h12l-8 16 28-20h-16l12-12z&quot;&gt;&lt;/path&gt;
&lt;/symbol&gt;
&lt;symbol id=&quot;icon-notification&quot; viewBox=&quot;0 0 32 32&quot;&gt;
&lt;title&gt;notification&lt;/title&gt;
&lt;path class=&quot;path1&quot; d=&quot;M16 3c-3.472 0-6.737 1.352-9.192 3.808s-3.808 5.72-3.808 9.192c0 3.472 1.352 6.737 3.808 9.192s5.72 3.808 9.192 3.808c3.472 0 6.737-1.352 9.192-3.808s3.808-5.72 3.808-9.192c0-3.472-1.352-6.737-3.808-9.192s-5.72-3.808-9.192-3.808zM16 0v0c8.837 0 16 7.163 16 16s-7.163 16-16 16c-8.837 0-16-7.163-16-16s7.163-16 16-16zM14 22h4v4h-4zM14 6h4v12h-4z&quot;&gt;&lt;/path&gt;
&lt;/symbol&gt;
&lt;/defs&gt;
&lt;/svg&gt;

&lt;body&gt;
  &lt;div id=&quot;root&quot;&gt;&lt;/div&gt;
  &lt;script src=&quot;/built/bundle.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;
&lt;/body&gt;
&lt;/html&gt;
* Connection #1 to host singh.hbot.dev left intact
</code></pre>
<p>Proceed on next steps</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.7/deploy/manifests/00-crds.yaml

customresourcedefinition.apiextensions.k8s.io/certificates.certmanager.k8s.io created
customresourcedefinition.apiextensions.k8s.io/challenges.certmanager.k8s.io created
customresourcedefinition.apiextensions.k8s.io/clusterissuers.certmanager.k8s.io created
customresourcedefinition.apiextensions.k8s.io/issuers.certmanager.k8s.io created
customresourcedefinition.apiextensions.k8s.io/orders.certmanager.k8s.io created
$
$ kubectl apply \
&gt;    -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.7/deploy/manifests/00-crds.yaml

customresourcedefinition.apiextensions.k8s.io/certificates.certmanager.k8s.io configured
customresourcedefinition.apiextensions.k8s.io/challenges.certmanager.k8s.io configured
customresourcedefinition.apiextensions.k8s.io/clusterissuers.certmanager.k8s.io configured
customresourcedefinition.apiextensions.k8s.io/issuers.certmanager.k8s.io configured
customresourcedefinition.apiextensions.k8s.io/orders.certmanager.k8s.io configured
$
$ kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=&quot;true&quot;

namespace/cert-manager labeled
$
$ helm repo add jetstack https://charts.jetstack.io
&quot;jetstack&quot; has been added to your repositories
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the &quot;jetstack&quot; chart repository
...Successfully got an update from the &quot;stable&quot; chart repository
Update Complete. ⎈ Happy Helming!⎈
</code></pre>
<p><code>install cert-manager</code></p>
<pre class="lang-sh prettyprint-override"><code>$ helm install --name cert-manager --namespace cert-manager jetstack/cert-manager
NAME:   cert-manager
LAST DEPLOYED: Thu Mar 14 16:06:48 2019
NAMESPACE: cert-manager
STATUS: DEPLOYED

RESOURCES:
==&gt; v1/ClusterRole
NAME                                    AGE
cert-manager-edit                       3s
cert-manager-view                       3s
cert-manager-webhook:webhook-requester  3s

==&gt; v1/Pod(related)
NAME                                      READY  STATUS             RESTARTS  AGE
cert-manager-6f68b58796-w44tn             0/1    ContainerCreating  0         3s
cert-manager-cainjector-67b4696847-l2lhb  0/1    ContainerCreating  0         3s
cert-manager-webhook-6f58884b96-gh52r     0/1    ContainerCreating  0         3s

==&gt; v1/Service
NAME                  TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)  AGE
cert-manager-webhook  ClusterIP  10.51.250.12  &lt;none&gt;       443/TCP  3s

==&gt; v1/ServiceAccount
NAME                     SECRETS  AGE
cert-manager             1        3s
cert-manager-cainjector  1        3s
cert-manager-webhook     1        3s

==&gt; v1alpha1/Certificate
NAME                              AGE
cert-manager-webhook-ca           3s
cert-manager-webhook-webhook-tls  3s

==&gt; v1alpha1/Issuer
NAME                           AGE
cert-manager-webhook-ca        2s
cert-manager-webhook-selfsign  3s

==&gt; v1beta1/APIService
NAME                                  AGE
v1beta1.admission.certmanager.k8s.io  3s

==&gt; v1beta1/ClusterRole
NAME                     AGE
cert-manager             3s
cert-manager-cainjector  3s

==&gt; v1beta1/ClusterRoleBinding
NAME                                 AGE
cert-manager                         3s
cert-manager-cainjector              3s
cert-manager-webhook:auth-delegator  3s

==&gt; v1beta1/Deployment
NAME                     READY  UP-TO-DATE  AVAILABLE  AGE
cert-manager             0/1    1           0          3s
cert-manager-cainjector  0/1    1           0          3s
cert-manager-webhook     0/1    1           0          3s

==&gt; v1beta1/RoleBinding
NAME                                                AGE
cert-manager-webhook:webhook-authentication-reader  3s

==&gt; v1beta1/ValidatingWebhookConfiguration
NAME                  AGE
cert-manager-webhook  2s


NOTES:
cert-manager has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://docs.cert-manager.io/en/latest/reference/issuers.html

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://docs.cert-manager.io/en/latest/reference/ingress-shim.html
</code></pre>
<p>Apply modified <code>staging-issuer.yaml and production-issuer.yaml</code>.</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl apply -f staging-issuer.yaml
issuer.certmanager.k8s.io/letsencrypt-staging created
$ kubectl apply -f production-issuer.yaml
issuer.certmanager.k8s.io/letsencrypt-prod created
</code></pre>
<p>Edit my <code>ingress.yaml</code> and apply it with</p>
<pre class="lang-sh prettyprint-override"><code>    kubernetes.io/ingress.class: &quot;nginx&quot;    
    certmanager.k8s.io/issuer: &quot;letsencrypt-staging&quot;
    certmanager.k8s.io/acme-challenge-type: http01
</code></pre>
<p>I found the <code>certificate</code>, but when I <code>describe</code> it <code>Events</code> is <code>none</code>!</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get certificate
NAME
quickstart-example-tls
$ kubectl describe certificate quickstart-example-tls
Name:         quickstart-example-tls
Namespace:    default
Labels:       &lt;none&gt;
Annotations:  &lt;none&gt;
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Creation Timestamp:  2019-03-14T09:17:11Z
  Generation:          1
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  kuard
    UID:                   f30e819b-4639-11e9-a2d5-42010a9400fd
  Resource Version:        2243137
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/quickstart-example-tls
  UID:                     f311c99d-4639-11e9-a2d5-42010a9400fd
Spec:
  Acme:
    Config:
      Domains:
        singh.hbot.dev
      Http 01:
        Ingress Class:  nginx
  Dns Names:
    singh.hbot.dev
  Issuer Ref:
    Kind:       Issuer
    Name:       letsencrypt-staging
  Secret Name:  quickstart-example-tls
Status:
  Conditions:
    Last Transition Time:  2019-03-14T09:17:11Z
    Message:               Certificate is up to date and has not expired
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2019-06-12T08:16:05Z
Events:                    &lt;none&gt;
</code></pre>
<p>Then I check <code>secret</code>. The docs says</p>
<blockquote>
<p>Once complete, cert-manager will have created a secret with the details of the certificate based on the secret used in the ingress resource. You can use the describe command as well to see some details:</p>
</blockquote>
<p>Although I don't have <code>ca.crt</code>. I decided to moved on.</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get secret
NAME                                   TYPE                                  DATA   AGE
default-token-vnngd                    kubernetes.io/service-account-token   3      10d
letsencrypt-prod                       Opaque                                1      3d1h
letsencrypt-staging                    Opaque                                1      3d1h
quickstart-example-tls                 kubernetes.io/tls                     3      3d1h
quickstart-nginx-ingress-token-c4tjk   kubernetes.io/service-account-token   3      58m
singh-dev-staging-tls                  kubernetes.io/tls                     3      21h
singh-secret                           kubernetes.io/tls                     3      22h
$ kubectl describe secret quickstart-example-tls
Name:         quickstart-example-tls
Namespace:    default
Labels:       certmanager.k8s.io/certificate-name=quickstart-example-tls
Annotations:  certmanager.k8s.io/alt-names: singh.hbot.dev
              certmanager.k8s.io/common-name: singh.hbot.dev
              certmanager.k8s.io/ip-sans:
              certmanager.k8s.io/issuer-kind: Issuer
              certmanager.k8s.io/issuer-name: letsencrypt-staging

Type:  kubernetes.io/tls

Data
====
tls.key:  1675 bytes
ca.crt:   0 bytes
tls.crt:  3545 bytes
</code></pre>
<p>Change <code>ingress.yaml</code> to be <code>production</code> and <code>apply</code>.</p>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl apply -f ingress.yaml
ingress.extensions/kuard created
</code></pre>
<p>Remove <code>secret</code></p>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl delete secret quickstart-example-tls
secret &quot;quickstart-example-tls&quot; deleted
</code></pre>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl get certificate
NAME
quickstart-example-tls
sixteen:cert-mgr hellohbot$ kubectl describe certificate quickstart-example-tls
Name:         quickstart-example-tls
Namespace:    default
Labels:       &lt;none&gt;
Annotations:  &lt;none&gt;
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Creation Timestamp:  2019-03-14T09:32:45Z
  Generation:          1
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  kuard
    UID:                   1fab9656-463c-11e9-a2d5-42010a9400fd
  Resource Version:        2246373
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/quickstart-example-tls
  UID:                     1facf771-463c-11e9-a2d5-42010a9400fd
Spec:
  Acme:
    Config:
      Domains:
        singh.hbot.dev
      Http 01:
        Ingress Class:  nginx
  Dns Names:
    singh.hbot.dev
  Issuer Ref:
    Kind:       Issuer
    Name:       letsencrypt-staging
  Secret Name:  quickstart-example-tls
Status:
  Conditions:
    Last Transition Time:  2019-03-14T09:34:06Z
    Message:               Certificate is up to date and has not expired
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2019-06-12T08:34:04Z
Events:
  Type    Reason              Age   From          Message
  ----    ------              ----  ----          -------
  Normal  Generated           33s   cert-manager  Generated new private key
  Normal  GenerateSelfSigned  33s   cert-manager  Generated temporary self signed certificate
  Normal  OrderCreated        33s   cert-manager  Created Order resource &quot;quickstart-example-tls-1671619353&quot;
  Normal  OrderComplete       6s    cert-manager  Order &quot;quickstart-example-tls-1671619353&quot; completed successfully
  Normal  CertIssued          6s    cert-manager  Certificate issued successfully
</code></pre>
<p>Check <code>order</code></p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl describe order quickstart-example-tls-1671619353
Name:         quickstart-example-tls-1671619353
Namespace:    default
Labels:       acme.cert-manager.io/certificate-name=quickstart-example-tls
Annotations:  &lt;none&gt;
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Order
Metadata:
  Creation Timestamp:  2019-03-14T09:33:39Z
  Generation:          1
  Owner References:
    API Version:           certmanager.k8s.io/v1alpha1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Certificate
    Name:                  quickstart-example-tls
    UID:                   1facf771-463c-11e9-a2d5-42010a9400fd
  Resource Version:        2246369
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/orders/quickstart-example-tls-1671619353
  UID:                     3fd25e87-463c-11e9-a2d5-42010a9400fd
Spec:
  Config:
    Domains:
      singh.hbot.dev
    Http 01:
      Ingress Class:  nginx
  Csr:                MIIC...RQ8=
  Dns Names:
    singh.hbot.dev
  Issuer Ref:
    Kind:  Issuer
    Name:  letsencrypt-staging
Status:
  Certificate:  LS0t...LQo=
  Challenges:
    Authz URL:  https://acme-staging-v02.api.letsencrypt.org/acme/authz/CkYZY5sWsaEq0uI2l1D2yyQwAjA1kl0_1uFsVY7UDqk
    Config:
      Http 01:
        Ingress Class:  nginx
    Dns Name:           singh.hbot.dev
    Issuer Ref:
      Kind:      Issuer
      Name:      letsencrypt-staging
    Key:         tRxDXBXr_CYcEX1KzU9puQKg1pVZdmEXi7jGWyPAvTs.-kMH8oyhdhqKbua2D8gLPi8FxbeW7rYKBB6w1gMRw2w
    Token:       tRxDXBXr_CYcEX1KzU9puQKg1pVZdmEXi7jGWyPAvTs
    Type:        http-01
    URL:         https://acme-staging-v02.api.letsencrypt.org/acme/challenge/CkYZY5sWsaEq0uI2l1D2yyQwAjA1kl0_1uFsVY7UDqk/270336074
    Wildcard:    false
  Finalize URL:  https://acme-staging-v02.api.letsencrypt.org/acme/finalize/8521062/26692657
  State:         valid
  URL:           https://acme-staging-v02.api.letsencrypt.org/acme/order/8521062/26692657
Events:
  Type    Reason      Age    From          Message
  ----    ------      ----   ----          -------
  Normal  Created     4m27s  cert-manager  Created Challenge resource &quot;quickstart-example-tls-1671619353-0&quot; for domain &quot;singh.hbot.dev&quot;
  Normal  OrderValid  4m     cert-manager  Order completed successfully
</code></pre>
<p><strong>Solution:</strong>
Thanks to <code>Harsh Manvar</code></p>
<p>Confirm my <code>issuer</code> url from the running <code>issuer</code></p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get issuer letsencrypt-prod -o yaml
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {&quot;apiVersion&quot;:&quot;certmanager.k8s.io/v1alpha1&quot;,&quot;kind&quot;:&quot;Issuer&quot;,&quot;metadata&quot;:{&quot;annotations&quot;:{},&quot;name&quot;:&quot;letsencrypt-prod&quot;,&quot;namespace&quot;:&quot;default&quot;},&quot;spec&quot;:{&quot;acme&quot;:{&quot;email&quot;:&quot;contact@hbot.io&quot;,&quot;http01&quot;:{},&quot;privateKeySecretRef&quot;:{&quot;name&quot;:&quot;letsencrypt-prod&quot;},&quot;server&quot;:&quot;https://acme-v02.api.letsencrypt.org/directory&quot;}}}
  creationTimestamp: &quot;2019-03-14T09:12:11Z&quot;
  generation: 1
  name: letsencrypt-prod
  namespace: default
  resourceVersion: &quot;2242148&quot;
  selfLink: /apis/certmanager.k8s.io/v1alpha1/namespaces/default/issuers/letsencrypt-prod
  uid: 405fa7af-4639-11e9-a2d5-42010a9400fd
spec:
  acme:
    email: contact@hbot.io
    http01: {}
    privateKeySecretRef:
      name: letsencrypt-prod
    server: https://acme-v02.api.letsencrypt.org/directory
status:
  acme:
    uri: https://acme-v02.api.letsencrypt.org/acme/acct/53068205
  conditions:
  - lastTransitionTime: &quot;2019-03-14T09:12:12Z&quot;
    message: The ACME account was registered with the ACME server
    reason: ACMEAccountRegistered
    status: &quot;True&quot;
    type: Ready
</code></pre>
<p>Check my <code>ingress</code></p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl get ingress --all-namespaces
NAMESPACE   NAME    HOSTS            ADDRESS         PORTS     AGE
default     kuard   singh.hbot.dev   35.198.217.71   80, 443   43m
$ kubectl describe ingress
Name:             kuard
Namespace:        default
Address:          35.198.217.71
Default backend:  default-http-backend:80 (10.48.0.7:8080)
TLS:
  quickstart-example-tls terminates singh.hbot.dev
Rules:
  Host            Path  Backends
  ----            ----  --------
  singh.hbot.dev
                  /   kuard:80 (&lt;none&gt;)
Annotations:
  certmanager.k8s.io/acme-challenge-type:            http01
  certmanager.k8s.io/issuer:                         letsencrypt-prod
  kubectl.kubernetes.io/last-applied-configuration:  {&quot;apiVersion&quot;:&quot;extensions/v1beta1&quot;,&quot;kind&quot;:&quot;Ingress&quot;,&quot;metadata&quot;:{&quot;annotations&quot;:{&quot;certmanager.k8s.io/acme-challenge-type&quot;:&quot;http01&quot;,&quot;certmanager.k8s.io/issuer&quot;:&quot;letsencrypt-prod&quot;,&quot;kubernetes.io/ingress.class&quot;:&quot;nginx&quot;},&quot;name&quot;:&quot;kuard&quot;,&quot;namespace&quot;:&quot;default&quot;},&quot;spec&quot;:{&quot;rules&quot;:[{&quot;host&quot;:&quot;singh.hbot.dev&quot;,&quot;http&quot;:{&quot;paths&quot;:[{&quot;backend&quot;:{&quot;serviceName&quot;:&quot;kuard&quot;,&quot;servicePort&quot;:80},&quot;path&quot;:&quot;/&quot;}]}}],&quot;tls&quot;:[{&quot;hosts&quot;:[&quot;singh.hbot.dev&quot;],&quot;secretName&quot;:&quot;quickstart-example-tls&quot;}]}}

  kubernetes.io/ingress.class:  nginx
Events:
  Type    Reason             Age                From                      Message
  ----    ------             ----               ----                      -------
  Normal  CREATE             43m                nginx-ingress-controller  Ingress default/kuard
  Normal  CreateCertificate  43m                cert-manager              Successfully created Certificate &quot;quickstart-example-tls&quot;
  Normal  UPDATE             10m (x2 over 43m)  nginx-ingress-controller  Ingress default/kuard
  Normal  UpdateCertificate  10m                cert-manager              Successfully updated Certificate &quot;quickstart-example-tls&quot;
</code></pre>
<p>Change <code>issuer</code> to <code>prod</code></p>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl apply -f ingress.yaml
ingress.extensions/kuard configured
</code></pre>
<p>Remove old <code>secret</code> to trigger the process.</p>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl get secret
NAME                                   TYPE                                  DATA   AGE
default-token-vnngd                    kubernetes.io/service-account-token   3      10d
letsencrypt-prod                       Opaque                                1      3d2h
letsencrypt-staging                    Opaque                                1      3d2h
quickstart-example-tls                 kubernetes.io/tls                     3      33m
quickstart-nginx-ingress-token-c4tjk   kubernetes.io/service-account-token   3      103m
singh-dev-staging-tls                  kubernetes.io/tls                     3      21h
singh-secret                           kubernetes.io/tls                     3      23h
sixteen:cert-mgr hellohbot$ kubectl delete secret quickstart-example-tls
secret &quot;quickstart-example-tls&quot; deleted
</code></pre>
<p>Check the new <code>certificate</code></p>
<pre class="lang-sh prettyprint-override"><code>sixteen:cert-mgr hellohbot$ kubectl get certificate
NAME
quickstart-example-tls
sixteen:cert-mgr hellohbot$ kubectl describe  certificate
Name:         quickstart-example-tls
Namespace:    default
Labels:       &lt;none&gt;
Annotations:  &lt;none&gt;
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Creation Timestamp:  2019-03-14T09:32:45Z
  Generation:          1
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  kuard
    UID:                   1fab9656-463c-11e9-a2d5-42010a9400fd
  Resource Version:        2252545
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/quickstart-example-tls
  UID:                     1facf771-463c-11e9-a2d5-42010a9400fd
Spec:
  Acme:
    Config:
      Domains:
        singh.hbot.dev
      Http 01:
        Ingress Class:  nginx
  Dns Names:
    singh.hbot.dev
  Issuer Ref:
    Kind:       Issuer
    Name:       letsencrypt-prod
  Secret Name:  quickstart-example-tls
Status:
  Conditions:
    Last Transition Time:  2019-03-14T10:06:53Z
    Message:               Certificate issuance in progress. Temporary certificate issued.
    Reason:                TemporaryCertificate
    Status:                False
    Type:                  Ready
Events:
  Type    Reason              Age                From          Message
  ----    ------              ----               ----          -------
  Normal  OrderCreated        33m                cert-manager  Created Order resource &quot;quickstart-example-tls-1671619353&quot;
  Normal  OrderComplete       33m                cert-manager  Order &quot;quickstart-example-tls-1671619353&quot; completed successfully
  Normal  CertIssued          33m                cert-manager  Certificate issued successfully
  Normal  Generated           19s (x2 over 33m)  cert-manager  Generated new private key
  Normal  GenerateSelfSigned  19s (x2 over 33m)  cert-manager  Generated temporary self signed certificate
  Normal  Cleanup             19s                cert-manager  Deleting old Order resource &quot;quickstart-example-tls-1671619353&quot;
  Normal  OrderCreated        19s                cert-manager  Created Order resource &quot;quickstart-example-tls-2367785339&quot;
</code></pre>

joe
<p>in ingress you are using issuer as <code>letsencrypt-staging</code> change it to production and also change <code>tls-secrets</code> it will work</p>

<p>Production url for let's encrypt issuer : <a href="https://acme-v02.api.letsencrypt.org/directory" rel="nofollow noreferrer">https://acme-v02.api.letsencrypt.org/directory</a></p>

<p>in the issuer you have used the staging url of let's encypt staging server change it to production URL and again try to get tls.cert and key it will run with https://</p>

<p>staging certificate some time not work with https and browser give error it is for testing purpose.</p>

<p>cert-manager and nginx ingress and other things are looking perfect as it should have to be. </p>
