<p>I'm trying to use the certificates obtained through digicert to enable https on my nginx-ingress. We've obtained a wildcard certificate and I have the following files.</p>

<pre><code>domain_name_2019-2021.csr
domain_name_2019-2021.key
domain_name_2019-2021.pem
DigiCertCA2_2019-2021.pem
star_domain_name_2019_2021.pem
TrustedRoot.pem
</code></pre>

<p>I've created the tls secrets by running the following commands</p>

<pre><code>kubectl create secret tls tls-secret --key ${KEY_FILE} --cert ${CERT_FILE}
</code></pre>

<p>And used these secrets in my ingress configuration like so</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-service
  namespace: default
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
spec:
  tls:
    - hosts:
       - {{ .Values.host }}
      secretName: tls-secret
  rules:
    - host: {{ .Values.host }}
      http:
        paths:
          - path: /
            backend:
              serviceName: service_name
              servicePort: 443
</code></pre>

<p>However when browse to subdomain.domain_name.com I get an invalid certificate with an error of <code>This certificate has not been verified by a third party</code>. And the certificate its using says <code>Kubernetes Ingress Controller Fake Certificate</code></p>

Matthew The Terrible
<p>you can follow <a href="https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html" rel="nofollow noreferrer">this</a>, to install Jetstack cert-manager, once you make this installed, please follow <a href="https://stackoverflow.com/questions/58423312/how-do-i-test-a-clusterissuer-solver/58436097?noredirect=1#comment103215785_58436097">this stackoverflow post</a>.</p>

<p>It will solve your query.</p>

<p>The current certificates created by you are not necessary for this, here the certificate will be automatically created by jetstack once it would be able to get the acme challenge verified, for that verification sake you need to map the DNS or hostname to the Load balancer IP of nginx.</p>

<p>This should solve your purpose to get http to https conversion</p>
