doc: correct PVC expansion documentation

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit is contained in:
Humble Chirammal 2020-06-10 15:46:27 +05:30 committed by mergify[bot]
parent 5fbc153e0f
commit 134e11e26e
2 changed files with 13 additions and 13 deletions

View File

@ -69,7 +69,7 @@ NOTE:
| | Creating and deleting snapshot | Alpha | >= v1.0.0 | >= v1.0.0 | Mimic (>=v13.0.0) | >= v1.14.0 |
| | Provision volume from snapshot | Alpha | >= v1.0.0 | >= v1.0.0 | Mimic (>=v13.0.0) | >= v1.14.0 |
| | Provision volume from another volume | - | - | - | - | - |
| | Resize volume | Beta | >= v2.0.0 | >= v1.1.0 | Mimic (>=v13.0.0) | >= v1.15.0 |
| | Expand volume | Beta | >= v2.0.0 | >= v1.1.0 | Mimic (>=v13.0.0) | >= v1.15.0 |
| | Metrics Support | Beta | >= v1.2.0 | >= v1.1.0 | Mimic (>=v13.0.0) | >= v1.15.0 |
| | Topology Aware Provisioning Support | Alpha | >= v2.1.0 | >= v1.1.0 | Mimic (>=v13.0.0) | >= v1.14.0 |
| CephFS | Dynamically provision, de-provision File mode RWO volume | Beta | >= v1.1.0 | >= v1.0.0 | Nautilus (>=14.2.2) | >= v1.14.0 |
@ -77,7 +77,7 @@ NOTE:
| | Creating and deleting snapshot | - | - | - | - | - |
| | Provision volume from snapshot | - | - | - | - | - |
| | Provision volume from another volume | - | - | - | - | - |
| | Resize volume | Beta | >= v2.0.0 | >= v1.1.0 | Nautilus (>=v14.2.2) | >= v1.15.0 |
| | Expand volume | Beta | >= v2.0.0 | >= v1.1.0 | Nautilus (>=v14.2.2) | >= v1.15.0 |
| | Metrics | Beta | >= v1.2.0 | >= v1.1.0 | Nautilus (>=v14.2.2) | >= v1.15.0 |
`NOTE`: The `Alpha` status reflects possible non-backward

View File

@ -10,13 +10,13 @@
## Prerequisite
- For filesystem resize to be supported for your kubernetes cluster, the
- For filesystem expansion to be supported for your kubernetes cluster, the
kubernetes version running in your cluster should be >= v1.15 and for block
volume resize support the kubernetes version should be >=1.16. Also,
`ExpandCSIVolumes` feature gate has to be enabled for the volume resize
volume expand support the kubernetes version should be >=1.16. Also,
`ExpandCSIVolumes` feature gate has to be enabled for the volume expand
functionality to work.
- The controlling StorageClass must have allowVolumeExpansion set to true.
- The controlling StorageClass must have `allowVolumeExpansion` set to `true`.
### Expand RBD PVCs
@ -126,8 +126,8 @@ metadata:
selfLink: ""
```
Now you can see the pvc status as `FileSystemResizePending`, once the kubelet
calls the NodeExpandVolume to resize the PVC on node, the `status conditions`
Now you can see the PVC status as `FileSystemResizePending`, once the kubelet
calls the NodeExpandVolume to expand the PVC on node, the `status conditions`
and `status` will be updated
```bash
@ -245,9 +245,9 @@ status:
phase: Bound
```
Now you can see the pvc stats as FileSystemResizePending, once the kubelet calls
the NodeExpandVolume to resize the PVC on node, the status conditions will be updated
and status.capacity.storage will be updated.
Now you can see the PVC stats as `FileSystemResizePending`, once the kubelet calls
the NodeExpandVolume to expand the PVC on node, the status conditions will be updated
and `status.capacity.storage` will be updated.
```bash
[$]kubectl get pvc
@ -326,7 +326,7 @@ Filesystem S
[$]kubectl edit pvc csi-cephfs-pvc
```
Check PVC status after editing the pvc storage
Check PVC status after editing the PVC storage
```yaml
apiVersion: v1
@ -367,7 +367,7 @@ metadata:
selfLink: ""
```
Now you can see the pvc status capacity storage is updated with request size
Now you can see the PVC status capacity storage is updated with request size
```bash
[$]kubectl get pvc