<p>I set up a cluster issuer, certificate, and ingress under my Kubernetes environment and everything is working fine as per status, but when I am connecting to the host as per my ingress, it's giving me  "Your connection is not private".</p>

<p><strong>CluserterIssuer</strong> output lastlines;-</p>

<pre><code>...
Conditions:
    Last Transition Time:  2020-02-16T10:21:24Z
    Message:               The ACME account was registered with the ACME server
    Reason:                ACMEAccountRegistered
    Status:                True
    Type:                  Ready
Events:                    &lt;none&gt;

</code></pre>

<p>Certificate output last lines :- </p>

<pre><code>Status:
  Conditions:
    Last Transition Time:  2020-02-16T10:24:06Z
    Message:               Certificate is up to date and has not expired
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2020-05-14T09:24:05Z
Events:                    &lt;none&gt;

</code></pre>

<p><strong>Ingress</strong> file:-</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
   name: b1-ingress  # change me
   namespace: b1
   annotations:
    kubernetes.io/ingress.class: "nginx"
    kubernetes.io/tls-acme: "true"
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
  tls:
  - hosts:
     - '*.testing.example.com'
    secretName: acme-crt
  rules:
  - host: flower.testing.example.com
    http:
      paths:
      - backend:
          serviceName: flower-service
          servicePort: 5555

  - host: hasura.testing.example.com
    http:
      paths:
      - backend:
          serviceName: hasura-service
          servicePort: 80

</code></pre>

me25
<p>Based on cert menager <a href="http://docs.cert-manager.io/en/release-0.7/tasks/issuing-certificates/ingress-shim.html#supported-annotations" rel="nofollow noreferrer">documentation</a></p>

<blockquote>
  <p><strong>certmanager.k8s.io/issuer</strong> - The Issuer must be in the <strong>same namespace</strong> as the Ingress resource.</p>
</blockquote>

<p>As @me25 confirmed in comments </p>

<blockquote>
  <p>yes everything worked when I copied secret in to namespace: b1 – me25</p>
</blockquote>

<p>The answer here was missing secret certificate in proper namespace.</p>

<p>The solution was to copy secret certificate to <code>namespace: b1</code>,same as the ingress.</p>

<hr>

<blockquote>
  <p>Do you know any better way other than a copy secrets</p>
</blockquote>

<p>This <a href="https://stackoverflow.com/questions/46297949/kubernetes-sharing-secret-across-namespaces">stackoverflow post</a> provide few tricks about copying secret from one namespace to other.</p>

<hr>

<p>Additional links:</p>

<ul>
<li><a href="https://itnext.io/automated-tls-with-cert-manager-and-letsencrypt-for-kubernetes-7daaa5e0cae4" rel="nofollow noreferrer">https://itnext.io/automated-tls-with-cert-manager-and-letsencrypt-for-kubernetes-7daaa5e0cae4</a></li>
<li><a href="https://cert-manager.io/docs/tutorials/acme/ingress/" rel="nofollow noreferrer">https://cert-manager.io/docs/tutorials/acme/ingress/</a></li>
</ul>
