From 80d4800d4b12503d7e3796b9271dea168a1fcc80 Mon Sep 17 00:00:00 2001 From: Anirudh Ramanathan Date: Thu, 14 Jul 2016 15:51:12 -0700 Subject: [PATCH] Added instructions on turning on dynamic provisioning for testing. HostPath volumes are not automatically provisioned unless we pass in `--enable-hostpath-provisioner` to the controller manager. This was not mentioned in the docs previously. --- examples/experimental/persistent-volume-provisioning/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/examples/experimental/persistent-volume-provisioning/README.md b/examples/experimental/persistent-volume-provisioning/README.md index ad66109e58224..e40891d3561af 100644 --- a/examples/experimental/persistent-volume-provisioning/README.md +++ b/examples/experimental/persistent-volume-provisioning/README.md @@ -51,8 +51,7 @@ There is no provisioner when running outside of any of those 3 cloud providers. A fourth provisioner is included for testing and development only. It creates HostPath volumes, which will never work outside of a single node cluster. It is not supported in any way except for -local for testing and development. - +local for testing and development. This provisioner may be used by passing `--enable-hostpath-provisioner=true` to the controller manager while bringing it up. When using the hack/local_up_cluster.sh script, this flag is turned off by default. It may be turned on by setting the environment variable `ENABLE_HOSTPATH_PROVISIONER` to true prior to running the script. ### User provisioning requests