<p>Everything in my Kubernetes configuration works great with a single TLS certificate. I define the cert as a <code>Secret</code> and reference it in my <code>Ingress</code> object configuration by name and my HTTPS traffic is served with the certificate. </p>

<p>My problem comes in when I try to use my other certificate as well. One of my certs has <code>www.DomainA.com</code> as the CN and <code>DomainA.com,DomainB.com,DomainC.com</code> as SAN's. The other one of my certs is a wildcard for <code>*.DomainA.com</code>.</p>

<p>When I add both certs to my Kubenetes configuration (with or without a defined <a href="http://kubernetes.io/docs/api-reference/extensions/v1beta1/definitions/#_v1beta1_ingresstls" rel="nofollow"><code>hosts</code></a> field for either/both), only the first specified cert is added in the interface and served to any traffic. </p>

<p>What is odd is that when I run a <code>kubectl describe ingress my-ingress</code> I see:</p>

<pre><code>TLS:
  non-wildcard-cert terminates DomainA.com,DomainB.com,DomainC.com
  wildcard-cert terminates *.DomainA.com
</code></pre>

<p>So I know both certs were picked up by Kubernetes, it just doesn't seem to be used (or stored) in GCP.</p>

<p>How can I use both of these certs?</p>

<p>Looks like, for now, GCP doesn't support the <a href="http://kubernetes.io/docs/api-reference/extensions/v1beta1/definitions/#_v1beta1_ingresstls" rel="nofollow">Kubernetes spec</a> correctly according to the <a href="https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/README.md#tls" rel="nofollow">GCE Ingress Controller doc</a>. When they do add the full SNI support from the spec, I should be able to do what I need.</p>

<p>I see that the <a href="https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx/examples/multi-tls" rel="nofollow">nginx Ingress controller has SNI support</a> but I only want to use the official, transparent, Google-maintained Ingress controller.</p>
