Kubernetes always gives 503 Service Temporarily Unavailable with multiple TLS Ingress

Solution 1:

It was caused by the Ingress config referencing the incorrect services name. After updating the Ingress reference to the service I no longer get a 503.

Solution 2:

You can get a 503 error from nginx when basic-auth is enable in the Ingress and the annotation nginx.ingress.kubernetes.io/auth-secret is referencing a non-existing secret.

Either adding the missing secret or removing all basic-auth annotations from the Ingress can resolve this situation.