2 ms·
Their proposed solution isn't really a solution either, and will probably make things worse. Current behavior - Kubernetes sends SIGTERM signal to your contain
by paxys 5y ago
Their proposed solution isn't really a solution either, and will probably make things worse.
Current behavior - Kubernetes sends SIGTERM signal to your container, it starts the shutdown process, stops the web server, and finishes up the requests in flight. Ingress controller continues to send some requests to the pod regardless, and they fail to connect. The client can handle these failures in whatever way it deems fit.
Their solution - Kubernetes sends SIGTERM signal, container ignores it and keeps taking new requests. After a while the process is forcefully killed, all requests in flight fail in unpredictable ways, and other resources (like DB connections) may be left dangling.