github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #44804 from humblec/glusterfs-rearrange 

Automatic merge from submit-queue (batch tested with PRs 44996, 44804)

Rearrange glusterfs artifacts to own directory.
pull/6/head
Kubernetes Submit Queue 2017-04-27 08:57:32 -07:00 committed by GitHub
parent dc92a6fcc7 b6665b2075
commit 120fd322bd
3 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
examples/persistent-volume-provisioning/README.md
View File

@ -121,7 +121,7 @@ When both `restuserkey` and `secretNamespace` + `secretName` is specified, the s
* `clusterid`: `630372ccdc720a92c681fb928f27b53f` is the ID of the cluster which will be used by Heketi when provisioning the volume. It can also be a list of clusterids, for ex:
"8452344e2becec931ece4e33c4674e4e,42982310de6c63381718ccfa6d8cf397". This is an optional parameter.
Example of a secret can be found in [glusterfs-provisioning-secret.yaml](glusterfs-provisioning-secret.yaml).
Example of a secret can be found in [glusterfs-secret.yaml](glusterfs/glusterfs-secret.yaml).
* `gidMin` + `gidMax` : The minimum and maximum value of GID range for the storage class. A unique value (GID) in this range ( gidMin-gidMax ) will be used for dynamically provisioned volumes. These are optional values. If not specified, the volume will be provisioned with a value between 2000-2147483647 which are defaults for gidMin and gidMax respectively.

0
examples/persistent-volume-provisioning/glusterfs-dp.yaml → examples/persistent-volume-provisioning/glusterfs/glusterfs-dp.yaml
View File

0
examples/persistent-volume-provisioning/glusterfs-provisioning-secret.yaml → examples/persistent-volume-provisioning/glusterfs/glusterfs-secret.yaml
View File