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
For applications that supports updating configuration at runtime, like pgbouncer or nginx, it would be nice to just reload the application inside a running container. Instead of restarting the whole Pod using a rolling update.
This is how I do it manually:
Change configmap/secret and apply it to the cluster
Exec into the container that has mounted the configmap/secret as a file.
Check if the mounted file is updated inside the container
reload application with kill -SIGHUP 1 or nginx -s reload or some other application specific command.
Questions:
Will it be safe?
Look into how does nginx ingress controller does it right now? It indeed never does rolling update but does have new configs!
The text was updated successfully, but these errors were encountered:
Yes it will be awesome to have this feature in place! e.g. in case of fluentd assume we have 50 nodes then it will take too much for rolling update of all pods in the daemonset; but if have restart of process then it will happen at sametime in all
I would also like to put in consideration for applications with required bootstrapping on start or restart. Unless this will be implemented towards very specifically defined apps or those running behind process managers. I'm not sure how this would work out, seems very diverse?
Suggested by Marton Szucs in slack channel:
For applications that supports updating configuration at runtime, like pgbouncer or nginx, it would be nice to just reload the application inside a running container. Instead of restarting the whole Pod using a rolling update.
This is how I do it manually:
kill -SIGHUP 1
ornginx -s reload
or some other application specific command.Questions:
The text was updated successfully, but these errors were encountered: