diff options
| author | Jan Safranek <jsafrane@redhat.com> | 2016-09-23 16:33:06 +0200 |
|---|---|---|
| committer | Jan Safranek <jsafrane@redhat.com> | 2016-09-23 16:33:06 +0200 |
| commit | 9764f78a4f7548207cde41999f9f2099ee38eeaa (patch) | |
| tree | 24bc0f2fd2c26a5ff514f022475d5d2fa1ece9f9 | |
| parent | 30ff069e6484007c665c735f180a272075d243ce (diff) | |
Update storage API group in docs
| -rw-r--r-- | volume-provisioning.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/volume-provisioning.md b/volume-provisioning.md index 4ee217dc..408edf93 100644 --- a/volume-provisioning.md +++ b/volume-provisioning.md @@ -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`: |