Re:Zero-Downtime Kubernetes Deployments on AWS with EKS
by jchw on Monday March 10, 2025 @11:33PM
(#43328906)
Presumably, because it'd be annoying waiting for lame duck mode when you actually do want the application to terminate quickly. SIGKILL usually needs special privileges/root and doesn't give the application any time to clean-up/flush/etc. The other workaround I've seen is having the application clean-up immediately upon a second signal, which I reckon could also work, but either solution seems reasonable.
[ Parent
| on HN ]
Re:Zero-Downtime Kubernetes Deployments on AWS with EKS
by paranoidrobot on Tuesday March 11, 2025 @12:20AM
(#43329118)
Yeah, there were a bunch of reasons.
Using SIGTERM is a problem because it conflicts with other behavior.
For instance, if you use SIGTERM for this then you have a potential for the app quitting during the preStop, which will be detected as a crash by Kube and so restart your app.
Re:Zero-Downtime Kubernetes Deployments on AWS with EKS
by chippiewill on Tuesday March 11, 2025 @08:54AM
(#43331943)
> which will be detected as a crash by Kube and so restart your app.
I don't think kubernetes restarts pods that have been marked for termination