node-local-dns
should support graceful shutdown with the ready
plugin
#642
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
We are using
node-local-dns
with a CiliumLocal Redirect Policy as described here so we neednode-local-dns
to be able to become Not Ready once it receives aSIGTERM
so time is given for the Endpoint to stop receiving traffic and for requests to be directed tokube-dns
instead, before the pod is fully terminated. This will allow graceful rollouts of thenode-local-dns
daemonset.In #485 it was requested the
ready
plugin be added tonode-local-dns
but it was closed on the basis it wouldn't serve any purpose as it would behave the same way as thehealth
plugin. However I believe that's not the case and theready
plugin would allownode-local-dns
to gracefully shutdown, since once it receives aSIGTERM
the/ready
endpoint would start returning 503 which can be used in a Readiness Probe on the pod to determine the pod is shutting down and give time for the Endpoint to be removed when used with thehealth
pluginslameduck
setting.So I am again requesting the
ready
plugin be added to the plugins list here.The text was updated successfully, but these errors were encountered: