Update cloning docs to reflect beta for 1.16 (#16013)

Updates the feature status for VolumePVCDataSource to 1.16/beta in the
docs.
This commit is contained in:
John Griffith
2019-09-06 16:15:20 -06:00
committed by Kubernetes Prow Robot
parent 762bd879ac
commit 420afb2d9f
3 changed files with 18 additions and 12 deletions
@@ -682,7 +682,7 @@ spec:
## Volume Cloning ## Volume Cloning
{{< feature-state for_k8s_version="v1.15" state="alpha" >}} {{< feature-state for_k8s_version="v1.16" state="beta" >}}
Volume clone feature was added to support CSI Volume Plugins only. For details, see [volume cloning](/docs/concepts/storage/volume-pvc-datasource/). Volume clone feature was added to support CSI Volume Plugins only. For details, see [volume cloning](/docs/concepts/storage/volume-pvc-datasource/).
@@ -11,7 +11,7 @@ weight: 30
{{% capture overview %}} {{% capture overview %}}
{{< feature-state for_k8s_version="v1.15" state="alpha" >}} {{< feature-state for_k8s_version="v1.16" state="beta" >}}
This document describes the concept of cloning existing CSI Volumes in Kubernetes. Familiarity with [Volumes](/docs/concepts/storage/volumes) is suggested. This document describes the concept of cloning existing CSI Volumes in Kubernetes. Familiarity with [Volumes](/docs/concepts/storage/volumes) is suggested.
This feature requires VolumePVCDataSource feature gate to be enabled: This feature requires VolumePVCDataSource feature gate to be enabled:
@@ -40,6 +40,10 @@ Users need to be aware of the following when using this feature:
* Cloning support is only available for dynamic provisioners. * Cloning support is only available for dynamic provisioners.
* CSI drivers may or may not have implemented the volume cloning functionality. * CSI drivers may or may not have implemented the volume cloning functionality.
* You can only clone a PVC when it exists in the same namespace as the destination PVC (source and destination must be in the same namespace). * You can only clone a PVC when it exists in the same namespace as the destination PVC (source and destination must be in the same namespace).
* Cloning is only supported within the same Storage Class.
- Destination volume must be the same storage class as the source
- Default storage class can be used and storageClassName omitted in the spec
## Provisioning ## Provisioning
@@ -54,6 +58,7 @@ metadata:
spec: spec:
accessModes: accessModes:
- ReadWriteOnce - ReadWriteOnce
storageClassName: cloning
resources: resources:
requests: requests:
storage: 5Gi storage: 5Gi
@@ -175,7 +175,8 @@ different Kubernetes components.
| `TokenRequestProjection` | `false` | Alpha | 1.11 | 1.11 | | `TokenRequestProjection` | `false` | Alpha | 1.11 | 1.11 |
| `TokenRequestProjection` | `true` | Beta | 1.12 | | | `TokenRequestProjection` | `true` | Beta | 1.12 | |
| `TTLAfterFinished` | `false` | Alpha | 1.12 | | | `TTLAfterFinished` | `false` | Alpha | 1.12 | |
| `VolumePVCDataSource` | `false` | Alpha | 1.15 | | | `VolumePVCDataSource` | `false` | Alpha | 1.15 | 1.15 |
| `VolumePVCDataSource` | `true` | Beta | 1.16 | |
| `VolumeScheduling` | `false` | Alpha | 1.9 | 1.9 | | `VolumeScheduling` | `false` | Alpha | 1.9 | 1.9 |
| `VolumeScheduling` | `true` | Beta | 1.10 | 1.12 | | `VolumeScheduling` | `true` | Beta | 1.10 | 1.12 |
| `VolumeScheduling` | `true` | GA | 1.13 | | | `VolumeScheduling` | `true` | GA | 1.13 | |