Justin Santa Barbara 3cdbfc98af AWS: strong-typing for k8s vs aws volume ids ... We are more liberal in what we accept as a volume id in k8s, and indeed we ourselves generate names that look like `aws://<zone>/<id>` for dynamic volumes. This volume id (hereafter a KubernetesVolumeID) cannot directly be compared to an AWS volume ID (hereafter an awsVolumeID). We introduce types for each, to prevent accidental comparison or confusion. Issue #35746		2016-11-02 09:42:55 -04:00
..
admission	AWS: strong-typing for k8s vs aws volume ids	2016-11-02 09:42:55 -04:00
auth	include multiple versions in clientset	2016-10-29 13:30:47 -07:00
client/auth	autogenerated	2016-10-21 17:32:32 -07:00
scheduler	Support opaque integer resource accounting.	2016-10-28 10:15:13 -07:00
webhook	Replace negotiation with a new method that can extract info	2016-10-28 11:30:11 -04:00