From 606caa3d7b31b562ee830e2dde3e4e0bf4fb9b43 Mon Sep 17 00:00:00 2001 From: Robert Rati Date: Sat, 8 Jul 2017 22:05:12 -0400 Subject: [PATCH] Add docs for running cloud-controller-manager with persistent volume labeling --- docs/tasks/administer-cluster/running-cloud-controller.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/tasks/administer-cluster/running-cloud-controller.md b/docs/tasks/administer-cluster/running-cloud-controller.md index 21b278b74c..72a71a2a11 100644 --- a/docs/tasks/administer-cluster/running-cloud-controller.md +++ b/docs/tasks/administer-cluster/running-cloud-controller.md @@ -33,3 +33,5 @@ Once your code is ready, you must import that code into `cloud-controller-manage To run `cloud-controller-manager`, add it to your existing Kubernetes cluster as a Master component. All other master components except `kube-controller-manager` can be run without any changes. The `kube-controller-manager` should not run any cloud-specific controllers, since the `cloud-controller-manager` takes over this responsibility. To prevent the `kube-controller-manager` from running cloud-specific controllers, you must set the `--cloud-provider` flag in `kube-controller-manager` to `external`. + +The `kube-apiserver` should not run the Persistent Volume Label admission controller either since the `cloud-controller-manager` takes over labeling persistent volumes. To prevent the Persistent Volume Label admission plugin from running, make sure the `kube-apiserver` has a `--admission-control` flag with a value that does not include `PersistentVolumeLabel`.