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

Merge pull request #33371 from jsafrane/api-endpoint 

Automatic merge from submit-queue

Update storage API group in docs

It reflects actual state of implementation (i.e. the API group was already changed in 1.4).
pull/6/head
Kubernetes Submit Queue 2016-09-27 08:59:47 -07:00 committed by GitHub
parent 091721d9dc f09056d1d0
commit 354f003c34
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/proposals/volume-provisioning.md
View File

@ -77,7 +77,7 @@ We propose that:
1. For the base impelementation storage class and volume selectors are mutually exclusive.
2. An api object will be incubated in extensions/v1beta1 named `storage` to hold the a `StorageClass`
2. An api object will be incubated in storage.k8s.io/v1beta1 to hold the a `StorageClass`
API resource. Each StorageClass object contains parameters required by the provisioner to provision volumes of that class. These parameters are opaque to the user.
3. `PersistentVolume.Spec.Class` attribute is added to volumes. This attribute
@ -155,7 +155,7 @@ Existing behavior is un-changed for claims that do not specify `claim.Spec.Class
A new API group should hold the API for storage classes, following the pattern
of autoscaling, metrics, etc. To allow for future storage-related APIs, we
should call this new API group `storage` and incubate in extensions/v1beta1.
should call this new API group `storage.k8s.io` and incubate in storage.k8s.io/v1beta1.
Storage classes will be represented by an API object called `StorageClass`: