From 240094e061cb79258b9289bb3ae0805708fb1f05 Mon Sep 17 00:00:00 2001 From: Li Wei Date: Tue, 14 Nov 2017 19:49:52 +0800 Subject: [PATCH] fix volume mount error in stackube-proxy As kubernetes support mount propogation now, the "shared" propogation type is not needed any more and would cause volume mount error. Change-Id: Idfa718ff7f0591ed246dc06f4a78c886abe9efe2 Signed-off-by: Li Wei --- deployment/stackube-proxy.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/deployment/stackube-proxy.yaml b/deployment/stackube-proxy.yaml index c3695cd..9c3c0d9 100644 --- a/deployment/stackube-proxy.yaml +++ b/deployment/stackube-proxy.yaml @@ -109,9 +109,7 @@ spec: name: stackube-config key: kubernetes-port volumeMounts: - # mount as shared because mount propagation is not supported - # in kubernetes api yet. - - mountPath: /var/run/netns:shared + - mountPath: /var/run/netns name: netns - mountPath: /etc/ssl/certs name: certs @@ -165,4 +163,4 @@ apiVersion: v1 kind: ServiceAccount metadata: name: stackube-proxy - namespace: kube-system \ No newline at end of file + namespace: kube-system