From f2910697deae132eae48b85de174f180c279ca18 Mon Sep 17 00:00:00 2001 From: Michal Nasiadka Date: Wed, 11 Jan 2023 10:10:09 +0100 Subject: [PATCH] cinder-csi: Run controllerplugin in CNI network Currently one cinder-csi-nodeplugin pod is always in Pending state, because the nodeplugin and controllerplugin deployments share the same TCP port. Adapt the manifest to upstream cinder-csi manifest, and run controllerplugin in CNI network and nodeplugin in host networking. Change-Id: Idbec5e8e64096a1e1a932da79e656f97f8db1144 (cherry picked from commit b578bd8a78d890ad32aeb6066cc22ece165f54e2) --- .../common/templates/kubernetes/fragments/enable-cinder-csi.sh | 1 - 1 file changed, 1 deletion(-) diff --git a/magnum/drivers/common/templates/kubernetes/fragments/enable-cinder-csi.sh b/magnum/drivers/common/templates/kubernetes/fragments/enable-cinder-csi.sh index 524b5e98ed..7321d130a0 100644 --- a/magnum/drivers/common/templates/kubernetes/fragments/enable-cinder-csi.sh +++ b/magnum/drivers/common/templates/kubernetes/fragments/enable-cinder-csi.sh @@ -222,7 +222,6 @@ spec: app: csi-cinder-controllerplugin spec: serviceAccount: csi-cinder-controller-sa - hostNetwork: true tolerations: # Make sure the pod can be scheduled on master kubelet. - effect: NoSchedule