Nginx doesn't work after restarting upstream pod without restarting nginx itself.
See original GitHub issuePlease run microk8s.inspect
and attach the generated tarball to this issue.
We appreciate your feedback. Thank you for using microk8s. My Nginx connects to upstream headless service which serves statefulset webapi. I restart both the statefulset and the headless service without the nginx and it results in 502 Bad Gateway. I have to restart nginx to get the whole to work again. Is this the expected behaviour?
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Nginx doesn't work after restarting upstream pod ... - GitHub
My Nginx connects to upstream headless service which serves statefulset webapi. I restart both the statefulset and the headless service without ...
Read more >How to make a modification take affect without restarting nginx?
I wrote about how to restart nginx with zero downtime a while ago. This may be helpful for you.
Read more >Nginx container not restarting after shutdown in Kubernetes
This seems to be working as a failsafe to ensure that if the internal nginx process stops or doesn't even start, the container...
Read more >1725248 – nginx does not start after server reboot with "host ...
Description of problem: nginx does not start during server reboot with following error message: host not found in upstream "example.com" in ...
Read more >Gracefully Restart Nginx Web Server After Config Update
Explains how to restart the Nginx web server gracefully without t interrupting users current session under Linux/Unix/ *BSD operating ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
With reference to https://serverfault.com/questions/240476/how-to-force-nginx-to-resolve-dns-of-a-dynamic-hostname-everytime-when-doing-p/946404#946404, I change my nginx configuration accordingly but still doesn’t work:
What is the right resolver address that should be used?
There have no manual setting…Kubeneters Service discovery can parse it… The Nginx still work until the upstream server(Pod) was reboot…And it works again after reboot Nginx