You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cloudConfigFilePath=flag.String("cloud-config", "", "Path to GCE cloud provider config")
38
+
runAsController=flag.Bool("run-as-controller", false, "If set to true then the CSI driver runs the controller only and does not start the node service.")
Copy file name to clipboardExpand all lines: docs/kubernetes/user-guides/driver-install.md
+10-1
Original file line number
Diff line number
Diff line change
@@ -20,4 +20,13 @@ $ ./deploy/setup-project.sh
20
20
$ GCE_PD_SA_DIR=/my/safe/credentials/directory # Directory to get the service account key
21
21
$ GCE_PD_DRIVER_VERSION=stable # Driver version to deploy
22
22
$ ./deploy/kubernetes/deploy-driver.sh
23
-
```
23
+
```
24
+
25
+
## Running the controller separately
26
+
27
+
Traditionally, you run the CSI controllers with the GCE PD driver in the same Kubernetes cluster.
28
+
Though, in some scenarios you might want to run the CSI controllers (csi-provisioner, csi-attacher, etc.) together with the GCE PD controller service of this driver separately from the Kubernetes cluster it serves (while the GCE PD driver with an activated node service still runs inside the cluster).
29
+
Also, this may not necessarily have to be an GCE compute instance.
30
+
To support these cases, the GCE PD CSI driver plugin supports the following command line flag:
31
+
32
+
*`--run-as-controller=true` which allows you to only start the controller service (and not the node service) of the GCE PD driver.
0 commit comments