From 733de0e8190b3e7e79faabd1f9ad070d4843a549 Mon Sep 17 00:00:00 2001 From: Rob Rati Date: Fri, 8 Sep 2017 16:15:42 -0400 Subject: [PATCH] Added documentation around creating the InitializerConfiguration for the persistent volume label controller in the cloud-controller-manager (#5255) --- .../persistent-volume-label-initializer-config.yaml | 13 +++++++++++++ .../administer-cluster/running-cloud-controller.md | 4 ++++ 2 files changed, 17 insertions(+) create mode 100644 docs/tasks/administer-cluster/persistent-volume-label-initializer-config.yaml diff --git a/docs/tasks/administer-cluster/persistent-volume-label-initializer-config.yaml b/docs/tasks/administer-cluster/persistent-volume-label-initializer-config.yaml new file mode 100644 index 0000000000..4a2576cc2a --- /dev/null +++ b/docs/tasks/administer-cluster/persistent-volume-label-initializer-config.yaml @@ -0,0 +1,13 @@ +kind: InitializerConfiguration +apiVersion: admissionregistration.k8s.io/v1alpha1 +metadata: + name: pvlabel.kubernetes.io +initializers: + - name: pvlabel.kubernetes.io + rules: + - apiGroups: + - "" + apiVersions: + - "*" + resources: + - persistentvolumes diff --git a/docs/tasks/administer-cluster/running-cloud-controller.md b/docs/tasks/administer-cluster/running-cloud-controller.md index 0c45ade1c4..19bd860c95 100644 --- a/docs/tasks/administer-cluster/running-cloud-controller.md +++ b/docs/tasks/administer-cluster/running-cloud-controller.md @@ -32,3 +32,7 @@ To run `cloud-controller-manager`, add it to your existing Kubernetes cluster as 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`. + +For the `cloud-controller-manager` to label persistent volumes, initializers will need to be enabled and an InitializerConifguration needs to be added to the system. Follow [these instructions](/docs/admin/extensible-admission-controllers.md#enable-initializers-alpha-feature) to enable initializers. Use the following YAML to create the InitializerConfiguration: + +{% include code.html language="yaml" file="persistent-volume-label-initializer-config.yaml" ghlink="/docs/tasks/administer-cluster/persistent-volume-label-initializer-config.yaml" %}