You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
default-ssl-certificate, tls, ssl, certificate
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
OS (e.g. from /etc/os-release): Ubuntu 18.04.2 LTS
Kernel (e.g. uname -a): Linux master 4.15.0-47-generic Ingress only exposes internal node ip #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others:
What happened:
Connection refused when using default-ssl-certificate
What you expected to happen:
Connection should not be refused
How to reproduce it (as minimally and precisely as possible):
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
default-ssl-certificate, tls, ssl, certificate
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
NGINX Ingress controller version:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.24.0
Kubernetes version (use
kubectl version
):Environment:
uname -a
): Linux master 4.15.0-47-generic Ingress only exposes internal node ip #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
Connection refused when using
default-ssl-certificate
What you expected to happen:
Connection should not be refused
How to reproduce it (as minimally and precisely as possible):
ingress-nginx/deploy/mandatory.yaml
Lines 215 to 221 in 4efe549
--default-ssl-certificate=$(POD_NAMESPACE)/ingress-tls-cert
Anything else we need to know:
If you change in
ingress-nginx/deploy/mandatory.yaml
Line 214 in 4efe549
The text was updated successfully, but these errors were encountered: