From dc345d4bdfdd767c4880ffd257befc99243f4795 Mon Sep 17 00:00:00 2001 From: Saikrishna Edupuganti Date: Wed, 20 Mar 2019 12:46:27 -0700 Subject: [PATCH] Do not restart containerd, remove stop kubelet In case of containerd there is no need to restart. Restart for crio is needed when it manages the networks ns lifecycle. Removed the kubelet stop step which was a leftover from earlier device plugin install. Signed-off-by: Saikrishna Edupuganti --- clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml b/clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml index b6c1a77..3891dad 100644 --- a/clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml +++ b/clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml @@ -140,10 +140,8 @@ spec: - cp /tmp/cni/bin/{multus,sriov,vfioveth,jq} /host/opt/cni/bin/; /tmp/multus/install-multus-conf.sh; /tmp/multus/install-certs.sh; - systemctl stop kubelet; - echo "Restarting crio/containerd, kubelet"; - systemctl restart containerd; - systemctl restart crio; + echo "Restarting crio kubelet"; + systemctl restart crio; # Needed when crio manages ns lifecycle systemctl restart kubelet; volumeMounts: - name: usr-bin