Merge pull request #31106 from jsafrane/fix-aws-example

Automatic merge from submit-queue Fix description of AWS provisioner zones

Merge pull request #31106 from jsafrane/fix-aws-example
029f9b5b · Kubernetes Submit Queue · GitHub · 2b8e9562 · 22d43e1b · 029f9b5b
Commit 029f9b5b authored Aug 22, 2016 by Kubernetes Submit Queue Committed by GitHub Aug 22, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

README.md ...les/experimental/persistent-volume-provisioning/README.md +1 -1

No files found.
--- a/examples/experimental/persistent-volume-provisioning/README.md
+++ b/examples/experimental/persistent-volume-provisioning/README.md
@@ -62,7 +62,7 @@ parameters:
 ```

 * `type`: `io1`, `gp2`, `sc1`, `st1`. See AWS docs for details. Default: `gp2`.
-* `zone`: AWS zone. If not specified, a random zone in the same region as controller-manager will be chosen.
+* `zone`: AWS zone. If not specified, a random zone from those where Kubernetes cluster has a node is chosen.
 * `iopsPerGB`: only for `io1` volumes. I/O operations per second per GiB. AWS volume plugin multiplies this with size of requested volume to compute IOPS of the volume and caps it at 20 000 IOPS (maximum supported by AWS, see AWS docs).
 * `encrypted`: denotes whether the EBS volume should be encrypted or not. Valid values are `true` or `false`.
 * `kmsKeyId`: optional. The full Amazon Resource Name of the key to use when encrypting the volume. If none is supplied but `encrypted` is true, a key is generated by AWS. See AWS docs for valid ARN value.