We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CoreDNS needs SIGINT for the shutdown handlers to be called. I just implemented lameducking in the health middleware which will only work for SIGINT.
SIGTERM will just stop the process immediately.
The text was updated successfully, but these errors were encountered:
Looks like k8s just sends a SIGTERM, no SIGINT:
ann-m-jbelamaric:coredns jbelamaric$ kubectl -n kube-system logs coredns-579f8497d5-6bxkp --follow .:53 2018/01/11 19:24:46 [INFO] CoreDNS-1.0.0 2018/01/11 19:24:46 [INFO] linux/amd64, go1.9.1, a04eeb9c CoreDNS-1.0.0 linux/amd64, go1.9.1, a04eeb9c 2018/01/11 19:26:19 [INFO] SIGTERM: Terminating process ann-m-jbelamaric:coredns jbelamaric$
We could add a preStop hook that sends a SIGINT instead. https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
Sorry, something went wrong.
No branches or pull requests
CoreDNS needs SIGINT for the shutdown handlers to be called. I just implemented lameducking in the health middleware which will only work for SIGINT.
SIGTERM will just stop the process immediately.
The text was updated successfully, but these errors were encountered: