whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add a placeholder doc (#14643)

Browse Source 
* Add a placeholder doc

* Update persistent-volumes.md
This commit is contained in:
Hemant Kumar
2019-06-03 21:23:01 -04:00
committed by Kubernetes Prow Robot
parent 7acab64de6
commit 40ed4669b6
1 changed files with 7 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/storage/persistent-volumes.md
+7 -12
View File
@@ -226,15 +226,9 @@ CSI volume expansion requires enabling `ExpandCSIVolumes` feature gate and also
You can only resize volumes containing a file system if the file system is XFS, Ext3, or Ext4. You can only resize volumes containing a file system if the file system is XFS, Ext3, or Ext4.
When a volume contains a file system, the file system is only resized when a new Pod is started using When a volume contains a file system, the file system is only resized when a new Pod is using
the `PersistentVolumeClaim` in ReadWrite mode. Therefore, if a pod or deployment is using a volume and the `PersistentVolumeClaim` in ReadWrite mode. File system expansion is either done when Pod is starting up
you want to expand it, you need to delete or recreate the pod after the volume has been expanded by the cloud provider in the controller-manager. You can check the status of resize operation by running the `kubectl describe pvc` command: or is done when Pod is running and underlying file system supports online expansion.
```
kubectl describe pvc <pvc_name>
```
If the `PersistentVolumeClaim` has the status `FileSystemResizePending`, it is safe to recreate the pod using the PersistentVolumeClaim.
FlexVolumes allow resize if the driver is set with the `RequiresFSResize` capability to true. FlexVolumes allow resize if the driver is set with the `RequiresFSResize` capability to true.
The FlexVolume can be resized on pod restart. The FlexVolume can be resized on pod restart.
@@ -243,14 +237,15 @@ The FlexVolume can be resized on pod restart.
#### Resizing an in-use PersistentVolumeClaim #### Resizing an in-use PersistentVolumeClaim
Expanding in-use PVCs is an alpha feature. To use it, enable the `ExpandInUsePersistentVolumes` feature gate. Expanding in-use PVCs is a beta feature and is enabled by default via `ExpandInUsePersistentVolumes` feature gate.
In this case, you don't need to delete and recreate a Pod or deployment that is using an existing PVC. In this case, you don't need to delete and recreate a Pod or deployment that is using an existing PVC.
Any in-use PVC automatically becomes available to its Pod as soon as its file system has been expanded. Any in-use PVC automatically becomes available to its Pod as soon as its file system has been expanded.
This feature has no effect on PVCs that are not in use by a Pod or deployment. You must create a Pod which This feature has no effect on PVCs that are not in use by a Pod or deployment. You must create a Pod which
uses the PVC before the expansion can complete. uses the PVC before the expansion can complete.
Expanding in-use PVCs for FlexVolumes is added in release 1.13. To enable this feature use `ExpandInUsePersistentVolumes` and `ExpandPersistentVolumes` feature gates. The `ExpandPersistentVolumes` feature gate is already enabled by default. If the `ExpandInUsePersistentVolumes` is set, FlexVolume can be resized online without pod restart.
Similar to other volume types - FlexVolume volumes can also be expanded when in-use by a pod.
{{< note >}} {{< note >}}
**Note:** FlexVolume resize is possible only when the underlying driver supports resize. **Note:** FlexVolume resize is possible only when the underlying driver supports resize.
{{< /note >}} {{< /note >}}