<p>We are running an application on k8s cluster on GKE.</p>
<p>We are using an <code>nginx-ingress-controller</code> as external load-balancer Service which is reachable on, let's say, <a href="https://12.345.67.98" rel="nofollow noreferrer">https://12.345.67.98</a> . We are facing an issue that when we directly access the load-balancer on mentioned URL, we get a certificate warning because a self-signed &quot;Kubernetes Ingress Controller Fake Certificate&quot; is used.</p>
<p>We only have Ingress objects that are mapping our domains (e.g. app.our-company.com) to Kubernetes services. The nginx load-balancer is a Kubernetes Service with load-balancer type. For SSL/TLS for our domains <code>cert-manager</code> is used. There is no issue when accessing these domains, only when we directly access the load-balancer on the IP-Address.</p>
<p>Is there a way to somehow replace the certificate on the load-balancer, so it's not using the default fake certificate anymore?</p>

c_p_bacon
<p>You can override default SSL certificate during Ingress Controller helm installation.
Ref: <a href="https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml" rel="nofollow noreferrer">https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml</a></p>
<pre><code>  ## Additional command line arguments to pass to nginx-ingress-controller
  ## E.g. to specify the default SSL certificate you can use
  ## extraArgs:
  ##   default-ssl-certificate: &quot;&lt;namespace&gt;/&lt;secret_name&gt;&quot;
  extraArgs: {}
</code></pre>
