From f09056d1d0facffd0adba5140b9b706c917c7e2b Mon Sep 17 00:00:00 2001 From: Jan Safranek Date: Fri, 23 Sep 2016 16:33:06 +0200 Subject: [PATCH] Update storage API group in docs --- docs/proposals/volume-provisioning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/proposals/volume-provisioning.md b/docs/proposals/volume-provisioning.md index 4ee217dc79a..408edf93c49 100644 --- a/docs/proposals/volume-provisioning.md +++ b/docs/proposals/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`: