-
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
NGINX not reloading correctly #1203
Comments
@rikatz please test the image |
@rikatz please post the logs of the ingress pod |
@aledbf Your image is using the bogused nginx.tmpl (https://github.com/kubernetes/ingress/blob/master/controllers/nginx/rootfs/etc/nginx/template/nginx.tmpl#L576) I'm replacing it to $server.Hostname and will post the logs. |
@aledbf I have some confidential data here, but will try to clean the logs. Here's what happens:
This is in a loop, and while nginx.conf is configured correctly, nginx is not reloading. After changing the ingress object of one of the cases (like namespace2/ingress), ingress reloads correctly NGINX |
BTW, I'm using your image:
|
@rikatz this works as expected. Please keep in mind that any update (or initial sync) to ingress, secrets, endpoints and configmaps are asynchronous. Edit: the real issue here is the duplication of the warning in the log. |
@aledbf but Ingress only starts answering correctly after someone changes any Ingress Object. Before this, NGINX directs all the ingresses to default backend. |
@rikatz please update the image to |
OK, the template is ok, but the error still happens. I'm looking here to see if there's some secret causing this, or maybe this initial (a)sync is causing some issue to Ingress Controller. |
@aledbf So it seems it's working, but Ingress is taking too much time to load each of the secrets. The CA certificates are loaded immediately, but the TLS certs are not being loaded as fast as the CA. Isn't the case to load all the available secrets before reloading, in initial sync? And then reload as necessary? Thanks! |
@rikatz please test |
Yeap, this is working as expected o/ |
I'm using the latest Ingress Controller (following the 'master' branch), but using my on prod Kubernetes Cluster.
I have some Ingress misconfigured, and this is causing a loop message with them (ssl certs, etc), and also the continuous reload of the NGINX.
What happens here is that even with those reloads, it seems NGINX is not loading the nginx.conf file correctly.
The following is what happens:
The updates just seems to work, after all, when you change any Ingress Object. After changing any object, Nginx reloads correctly.
Thanks
The text was updated successfully, but these errors were encountered: