Skip to content

K
k3s
Commit 7a4f4fdc authored by k8s-merge-robot's avatar k8s-merge-robot Committed by GitHub
Browse files
Options

Merge pull request #28996 from zefciu/provisioning-docs

Automatic merge from submit-queue Info about enabling the hostpath provisioner The README for persistent volume provisioning had information about the hostpath provisioner for testing purposes, but lacked instructions on how to enable it.
parents 70594e82 2abf7040
Hide whitespace changes
Inline Side-by-side
Showing with 9 additions and 1 deletion
examples/experimental/persistent-volume-provisioning/README.md
View file @ 7a4f4fdc
......@@ -51,7 +51,15 @@ 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. 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.
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.
```
env ENABLE_HOSTPATH_PROVISIONER=true hack/local-up-cluster.sh
```
### User provisioning requests
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment