Only adds one cert to load balancers on GCE about kube-lego HOT 7 CLOSED

Just for notice, GCE Ingress supports SNI as today (2017.02.06).

from kube-lego.

If you're running all 3 stages of your app in the same cluster, you might be running into a known limitation with the GCE Ingress implementation. Specifically, the GCE Ingress doesn't support SNI, so it'll only ever configure 1 SSL certificate for the LoadBalancer. You can read more about it here: https://github.com/kubernetes/ingress/tree/master/controllers/gce#tls

from kube-lego.

Does this mean it would work if/when GCE Ingress supports SNI and nothing else would have to change?

from kube-lego.

works for me! 👍

from kube-lego.

@orian @schurig I can't find any reference to GCE SNI support, where have you found this?

from kube-lego.

@tsloughter I'm using Kubernetes Ingress resource and it supports multiple domains and one certificate. I cannot recall where I've found it. But I find a Ingress spec very helpful (even bit more than a webpage doc):
https://kubernetes.io/docs/api-reference/extensions/v1beta1/definitions/#_v1beta1_ingress

Kubernetes Ingress on GCE is built on top of Load Balancing. It creates a load balancer, the GCE Load Balancer supports SNI.

from kube-lego.

@orian yes, the ingress resource supports it but GCE LB does not (or at least hasn't worked for me and I can't find any docs saying it should work). The Kubernetes docs still say it is not supported: "This controller does not support SNI" from https://github.com/kubernetes/ingress/tree/master/controllers/gce

from kube-lego.