k3s/pkg/volume/gce_pd
k8s-merge-robot 07471cf90f Merge pull request #27553 from justinsb/pvc_zone_spreading_2
Automatic merge from submit-queue

AWS/GCE: Spread PetSet volume creation across zones, create GCE volumes in non-master zones

Long term we plan on integrating this into the scheduler, but in the
short term we use the volume name to place it onto a zone.
    
We hash the volume name so we don't bias to the first few zones.
    
If the volume name "looks like" a PetSet volume name (ending with
-<number>) then we use the number as an offset.  In that case we hash
the base name.
2016-06-22 01:22:16 -07:00
..
OWNERS add maintainers for each volume driver 2016-03-22 22:19:53 -07:00
attacher.go Controller wait for attach and exponential backoff 2016-06-20 18:19:55 -07:00
attacher_test.go Merge pull request #27553 from justinsb/pvc_zone_spreading_2 2016-06-22 01:22:16 -07:00
doc.go Add doc.go files for all volume plugins 2015-05-23 16:59:12 -04:00
gce_pd.go Remove spam log messages from gce pd 2016-06-15 09:34:08 -07:00
gce_pd_test.go Introduce new kubelet volume manager 2016-06-15 09:34:08 -07:00
gce_util.go GCE Multizone: Allow volumes to be created in non-master zone 2016-06-17 23:27:41 -04:00