<p>I'm still getting this privacy error
I'm still getting this privacy error
<a href="https://i.stack.imgur.com/JyWML.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JyWML.png" alt="enter image description here" /></a></p>
<p>the <code>issuer</code> generate a certificate and all things is good</p>
<p><a href="https://i.stack.imgur.com/lzTJe.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/lzTJe.png" alt="enter image description here" /></a></p>
<p>this is the ingress yaml:</p>
<pre><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: minimal-ingress
  namespace: default
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    kubernetes.io/tls-acme: &quot;true&quot;
    cert-manager.io/issuer: letsencrypt-nginx
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - &quot;myhost.com&quot;
      secretName: letsencrypt-nginx
  rules:
  - host: myhost.com
    http:
      paths:
        - path: /
          pathType: Prefix
          backend:
            service:  
              name: backend-service
              port:
                number: 3000
</code></pre>
<p>what could be the problem ?!</p>

Abd allah Khateeb
<p>It appears you are using <a href="https://cert-manager.io/docs/" rel="nofollow noreferrer">cert-manager</a> to generate CA signed certificates. The certificate status appears to be <code>True</code> which means cert-manager has successfully provisioned the certificate.</p>
<p>From the naming convention, I'm assuming your are using letsencrypt as <code>Issuer</code>.</p>
<p>However the browser is still throwing Certificate warning. This happens when you use the staging letsencrypt API endpoint, i.e. <code>https://acme-staging-v02.api.letsencrypt.org/directory</code></p>
<p>Cert-manager has <a href="https://cert-manager.io/docs/tutorials/acme/dns-validation/#:%7E:text=We%20have%20specified,org/directory." rel="nofollow noreferrer">documented</a> this too.</p>
<p>The staging API endpoint is there for you to <a href="https://letsencrypt.org/docs/staging-environment/#continuous-integration-development-testing" rel="nofollow noreferrer">experiment around and gain confidence</a> before using the production API endpoint, i.e. <code>https://acme-v02.api.letsencrypt.org/directory in your</code> in your <code>Issuer</code> spec.</p>
<p>Staging LetsEncrypt API endpoint has same rate limits as the Production LetsEncrypt API endpoint with few <a href="https://letsencrypt.org/docs/staging-environment/#rate-limits" rel="nofollow noreferrer">exceptions</a>.</p>
<p>Consider using Production LetsEncrypt API endpoint in your <code>Issuer</code> to avoid certificate related warnings.</p>
