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 b578bd8a78
)
This commit is contained in:
parent
a4d8145f88
commit
f2910697de
|
@ -222,7 +222,6 @@ spec:
|
||||||
app: csi-cinder-controllerplugin
|
app: csi-cinder-controllerplugin
|
||||||
spec:
|
spec:
|
||||||
serviceAccount: csi-cinder-controller-sa
|
serviceAccount: csi-cinder-controller-sa
|
||||||
hostNetwork: true
|
|
||||||
tolerations:
|
tolerations:
|
||||||
# Make sure the pod can be scheduled on master kubelet.
|
# Make sure the pod can be scheduled on master kubelet.
|
||||||
- effect: NoSchedule
|
- effect: NoSchedule
|
||||||
|
|
Loading…
Reference in New Issue