From d09282b3f023b390f133f6cb7c6d5f3adfa2a67c Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Wed, 1 Dec 2021 17:18:37 +0000 Subject: [PATCH] Tweak FlexVolume deprecation text --- .../concepts/storage/persistent-volumes.md | 24 +++++++++---------- content/en/docs/concepts/storage/volumes.md | 21 +++++++++------- 2 files changed, 24 insertions(+), 21 deletions(-) diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md index 619dbc8405..ea9538b20e 100644 --- a/content/en/docs/concepts/storage/persistent-volumes.md +++ b/content/en/docs/concepts/storage/persistent-volumes.md @@ -221,19 +221,19 @@ to `Retain`, including cases where you are reusing an existing PV. {{< feature-state for_k8s_version="v1.11" state="beta" >}} -Support for expanding PersistentVolumeClaims (PVCs) is now enabled by default. You can expand +Support for expanding PersistentVolumeClaims (PVCs) is enabled by default. You can expand the following types of volumes: -* gcePersistentDisk +* azureDisk +* azureFile * awsElasticBlockStore -* Cinder +* cinder (deprecated) +* {{< glossary_tooltip text="csi" term_id="csi" >}} +* flexVolume (deprecated) +* gcePersistentDisk * glusterfs * rbd -* Azure File -* Azure Disk -* Portworx -* FlexVolumes -* {{< glossary_tooltip text="CSI" term_id="csi" >}} +* portworxVolume You can only expand a PVC if its storage class's `allowVolumeExpansion` field is set to true. @@ -270,8 +270,8 @@ When a volume contains a file system, the file system is only resized when a new the PersistentVolumeClaim in `ReadWrite` mode. File system expansion is either done when a Pod is starting up or when a Pod is running and the underlying file system supports online expansion. -FlexVolumes allow resize if the driver is set with the `RequiresFSResize` capability to `true`. -The FlexVolume can be resized on Pod restart. +FlexVolumes (deprecated since Kubernetes v1.23) allow resize if the driver is configured with the +`RequiresFSResize` capability to `true`. The FlexVolume can be resized on Pod restart. #### Resizing an in-use PersistentVolumeClaim @@ -362,10 +362,10 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports The following types of PersistentVolume are deprecated. This means that support is still available but will be removed in a future Kubernetes release. -* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume - (**deprecated** in v1.23) * [`cinder`](/docs/concepts/storage/volumes/#cinder) - Cinder (OpenStack block storage) (**deprecated** in v1.18) +* [`flexVolume`](/docs/concepts/storage/volumes/#flexvolume) - FlexVolume + (**deprecated** in v1.23) * [`flocker`](/docs/concepts/storage/volumes/#flocker) - Flocker storage (**deprecated** in v1.22) * [`quobyte`](/docs/concepts/storage/volumes/#quobyte) - Quobyte volume diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 792ceae69b..7a0be7e524 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1155,8 +1155,7 @@ To learn about requesting space using a resource specification, see ## Out-of-tree volume plugins The out-of-tree volume plugins include -{{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} (CSI) -and FlexVolume. These plugins enable storage vendors to create custom storage plugins +{{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} (CSI), and also FlexVolume (which is deprecated). These plugins enable storage vendors to create custom storage plugins without adding their plugin source code to the Kubernetes repository. Previously, all volume plugins were "in-tree". The "in-tree" plugins were built, linked, compiled, @@ -1289,16 +1288,20 @@ are listed in [Types of Volumes](#volume-types). ### flexVolume -FlexVolume is an out-of-tree plugin interface that has existed in Kubernetes -since version 1.2 (before CSI). It uses an exec-based model to interface with -drivers. The FlexVolume driver binaries must be installed in a pre-defined volume -plugin path on each node and in some cases the control plane nodes as well. +{{< feature-state for_k8s_version="v1.23" state="deprecated" >}} -Pods interact with FlexVolume drivers through the `flexvolume` in-tree volume plugin. -For more details, see the [FlexVolume](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md) examples. +FlexVolume is an out-of-tree plugin interface that uses an exec-based model to interface +with storage drivers. The FlexVolume driver binaries must be installed in a pre-defined +volume plugin path on each node and in some cases the control plane nodes as well. + +Pods interact with FlexVolume drivers through the `flexVolume` in-tree volume plugin. +For more details, see the FlexVolume [README](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md#readme) document. {{< note >}} -FlexVolume is deprecated starting v1.23. Out-of-tree CSI driver is the recommended way to write volume driver in Kubernetes. Maintainers of FlexVolume driver should implement a CSI Driver and move users of FlexVolume to CSI. Users of FlexVolume should move their workloads to CSI Driver. +FlexVolume is deprecated. Using an out-of-tree CSI driver is the recommended way to integrate external storage with Kubernetes. + +Maintainers of FlexVolume driver should implement a CSI Driver and help to migrate users of FlexVolume drivers to CSI. +Users of FlexVolume should move their workloads to use the equivalent CSI Driver. {{< /note >}} ## Mount propagation