clearlinux/cloud-native-setup
2
0
Fork 0
mirror of https://github.com/clearlinux/cloud-native-setup.git synced 2026-08-19 05:27:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Do not restart containerd, remove stop kubelet

Browse Source 
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 <saikrishna.edupuganti@intel.com>
This commit is contained in:
Saikrishna Edupuganti
2019-03-20 12:46:27 -07:00
committed by Manohar Castelino
parent 935bb69cfd
commit dc345d4bdf
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
clr-k8s-examples/9-multi-network/multus-sriov-ds.yaml
+2 -4
View File
@@ -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