-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where is DefaultSSLCertificate used? #163
Comments
@rikatz please check the generated |
It's not there, so it's falling back to the first ssl enabled vhost (not the default one).
Ingress controller is not enabling the default cert in the default host
Ricardo P. Katz
… Em 23 de jan de 2017, às 18:01, Manuel Alejandro de Brito Fontes ***@***.***> escreveu:
@rikatz please check the generated nginx.conf file searching the default server. The file you see in the ssl certificate is the default certificate to use
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@aledbf This is the part of nginx.conf file that should have a '442' listen port:
I don't know if the used schema inside NGINX (listening as a stream on 443 port, and then directing it to a vhost) allows us to have a Default SSL Vhost. |
@aledbf here: https://github.com/kubernetes/ingress/blob/master/core/pkg/ingress/controller/controller.go#L821 I think there's something missing. I'm trying to do as follow:
I'm not being able to read the secret correctly (don't know why, but will keep trying), but I think this solves part of the problem, as Default Server is going to have a certificate for itself. The post step is to change also the template, but I'm not being able, by now, to read the Default SSL Certificate and transform it into something usable by the Default Server. |
Solved in #179 |
I'm configuring a new NGINX Ingress Controller here, and have the following startup command:
./nginx-ingress-controller --update-status=false --apiserver-host=https://10.200.83.12 --configmap=sistema/nginx-load-balancer-conf --default-ssl-certificate=sistema/tlspadrao --default-backend-service=sistema/default-backend --kubeconfig=/etc/kubernetes/kubeconfig.yaml
The ingress controller is able to configure the default ssl certificate (as the following):
But this file is not referenced anywhere on nginx configuration. Even on the default virtualhost (server_name _) there is no config of this default TLS certificate.
Also, I though this was necessary for vhosts that specify a 'tls' entry but no secret (as the following, using the default TLS certificate to this vhost):
So, what am I missing? Trying to see where in the code I can change this also :)
Thanks
The text was updated successfully, but these errors were encountered: