Disable the grace termination period for the calico/node pod

The grace period is unneccessary for calico/node and it delays restart of a new calico/node pod to take over routing and policy updates. Setting the grace period to 0 has the special meaning of doing a force deletion, which avoids a slow round-trip through the kubelet and API server. Fixes #55013

Disable the grace termination period for the calico/node pod
0cddb6b0 · Shaun Crampton · 40212c17 · 0cddb6b0
Commit 0cddb6b0 authored Nov 02, 2017 by Shaun Crampton
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 0 deletions

calico-node-daemonset.yaml ...ddons/calico-policy-controller/calico-node-daemonset.yaml +3 -0

No files found.
--- a/cluster/addons/calico-policy-controller/calico-node-daemonset.yaml
+++ b/cluster/addons/calico-policy-controller/calico-node-daemonset.yaml
@@ -24,6 +24,9 @@ spec:
        projectcalico.org/ds-ready: "true"
      hostNetwork: true
      serviceAccountName: calico
+      # Minimize downtime during a rolling upgrade or deletion; tell Kubernetes to do a "force
+      # deletion": https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods.
+      terminationGracePeriodSeconds: 0
      containers:
        # Runs calico/node container on each Kubernetes node.  This
        # container programs network policy and routes on each