From a05312f23b91213d16d7c60fa35401d9e3e28a76 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Thu, 30 Nov 2023 06:17:16 +0000 Subject: [PATCH 01/19] Added introduction about CSI Migration Modified the title from Type-of-volumes to In-tree volume plugin --- content/en/docs/concepts/storage/volumes.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 08be7f60e3..b4401b1ff0 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -58,9 +58,15 @@ Volumes cannot mount within other volumes (but see [Using subPath](#using-subpat for a related mechanism). Also, a volume cannot contain a hard link to anything in a different volume. -## Types of volumes {#volume-types} +## In-tree volume plugins and their CSI Migration progress {#volume-types} + +Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. +The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins.Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). + +{{< note >}} +When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. +{{< /note >}} -Kubernetes supports several types of volumes. ### awsElasticBlockStore (removed) {#awselasticblockstore} From 67ab54c25582843db04a12db3379f3ae51374aa5 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:15:48 +0900 Subject: [PATCH 02/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index b4401b1ff0..f211acbfbe 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -61,7 +61,7 @@ a different volume. ## In-tree volume plugins and their CSI Migration progress {#volume-types} Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. -The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins.Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). +The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. From 18aae9cb4b8a922e09ca7319130cc5f82af5fff6 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:15:57 +0900 Subject: [PATCH 03/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index f211acbfbe..8f83b9bc2b 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -64,7 +64,7 @@ Below is a list of In-tree plugins that are supported by Kubernetes and the stat The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} -When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. +When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing in-tree PVs and in-tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following in-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. {{< /note >}} From bec4fd8e2d378cfc88780721d449793c74cb675f Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:16:58 +0900 Subject: [PATCH 04/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 8f83b9bc2b..f378495472 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -60,7 +60,7 @@ a different volume. ## In-tree volume plugins and their CSI Migration progress {#volume-types} -Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. +Below is a list of in-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} From 200192734653493483a334877e63844493a904b3 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Wed, 20 Dec 2023 04:36:45 +0000 Subject: [PATCH 05/19] Added introduction about CSIMigration --- content/en/docs/concepts/storage/volumes.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index f378495472..95199de28d 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -58,15 +58,9 @@ Volumes cannot mount within other volumes (but see [Using subPath](#using-subpat for a related mechanism). Also, a volume cannot contain a hard link to anything in a different volume. -## In-tree volume plugins and their CSI Migration progress {#volume-types} - -Below is a list of in-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. -The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). - -{{< note >}} -When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing in-tree PVs and in-tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following in-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. -{{< /note >}} +## Types of volumes {#volume-types} +Kubernetes supports several types of volumes. ### awsElasticBlockStore (removed) {#awselasticblockstore} @@ -1040,6 +1034,12 @@ As a result, operators do not have to make any configuration changes to existing Storage Classes, PersistentVolumes or PersistentVolumeClaims (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. +{{< note >}} +* The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. +* Manifests that use in-tree volume plugins will also be used in the future without modifying. +* A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. +{{< /note >}} + The operations and features that are supported include: provisioning/delete, attach/detach, mount/unmount and resizing of volumes. From 68b0a2045c29210dffdefb04b6c851d960e283ff Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Wed, 20 Dec 2023 05:17:42 +0000 Subject: [PATCH 06/19] Deleted the contents that have been stated in the former paragraph --- content/en/docs/concepts/storage/volumes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 95199de28d..6c7fab5285 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1036,7 +1036,6 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste {{< note >}} * The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. -* Manifests that use in-tree volume plugins will also be used in the future without modifying. * A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. {{< /note >}} From 2a670f696ed92cba17ac635b35b9f258fa1f902a Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Thu, 21 Dec 2023 13:02:09 +0900 Subject: [PATCH 07/19] Update content/en/docs/concepts/storage/volumes.md Co-authored-by: Akihiro Motoki --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 6c7fab5285..c940e7bbe3 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1035,7 +1035,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. {{< note >}} -* The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. +* Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. * A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. {{< /note >}} From 3dd6d38a6bb5c644a4474b47110ccb31d5180940 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Thu, 21 Dec 2023 04:28:57 +0000 Subject: [PATCH 08/19] Modified the introduction about new pvs to make it more precise --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index c940e7bbe3..cc5093f093 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1036,7 +1036,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste {{< note >}} * Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. -* A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. +* New PVs with manifests that referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. {{< /note >}} The operations and features that are supported include: From 5afa73916ea40b3b4dead928501c779140ea1154 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Thu, 30 Nov 2023 06:17:16 +0000 Subject: [PATCH 09/19] Added introduction about CSI Migration Modified the title from Type-of-volumes to In-tree volume plugin --- content/en/docs/concepts/storage/volumes.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 94dd3757ea..2bc3dc4f7c 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -58,9 +58,15 @@ Volumes cannot mount within other volumes (but see [Using subPath](#using-subpat for a related mechanism). Also, a volume cannot contain a hard link to anything in a different volume. -## Types of volumes {#volume-types} +## In-tree volume plugins and their CSI Migration progress {#volume-types} + +Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. +The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins.Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). + +{{< note >}} +When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. +{{< /note >}} -Kubernetes supports several types of volumes. ### awsElasticBlockStore (removed) {#awselasticblockstore} From 6b6ad5f3f466e6ac1a9af9f1c807789364178180 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:15:48 +0900 Subject: [PATCH 10/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 2bc3dc4f7c..8a427befa7 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -61,7 +61,7 @@ a different volume. ## In-tree volume plugins and their CSI Migration progress {#volume-types} Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. -The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins.Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). +The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. From be5e34be972d819580073ea40a1b6c28738e1a04 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:15:57 +0900 Subject: [PATCH 11/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 8a427befa7..d00b28c7ec 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -64,7 +64,7 @@ Below is a list of In-tree plugins that are supported by Kubernetes and the stat The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} -When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing In trees PVs and In Tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following In-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. +When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing in-tree PVs and in-tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following in-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. {{< /note >}} From ce030879c8d182886de9833c2efde3759cb813f4 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Mon, 11 Dec 2023 20:16:58 +0900 Subject: [PATCH 12/19] Update content/en/docs/concepts/storage/volumes.md --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index d00b28c7ec..585705059e 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -60,7 +60,7 @@ a different volume. ## In-tree volume plugins and their CSI Migration progress {#volume-types} -Below is a list of In-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. +Below is a list of in-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). {{< note >}} From e0b4384748b99d6ae0803f93beb39053ce5185e6 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Wed, 20 Dec 2023 04:36:45 +0000 Subject: [PATCH 13/19] Added introduction about CSIMigration --- content/en/docs/concepts/storage/volumes.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 585705059e..d99b29c59b 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -58,15 +58,9 @@ Volumes cannot mount within other volumes (but see [Using subPath](#using-subpat for a related mechanism). Also, a volume cannot contain a hard link to anything in a different volume. -## In-tree volume plugins and their CSI Migration progress {#volume-types} - -Below is a list of in-tree plugins that are supported by Kubernetes and the status of their respective CSI Migrations progress. -The Container Storage Interface (CSI) was designed to help Kubernetes replace its existing, in-tree storage driver mechanisms - especially vendor specific plugins. Kubernetes support for the Container Storage Interface has been generally available since Kubernetes v1.13. For more details on CSI Migration, please refer to [Out-of-tree volume plugins](#out-of-tree-volume-plugins). - -{{< note >}} -When a Kubernetes cluster administrator updates a cluster to enable CSI migration, existing workloads that utilize PVCs which are backed by in-tree storage plugins will continue to function as they always have. Existing in-tree PVs and in-tree format yaml file will still be used in the future even after the migration is completed, and will not be left unprocessed or deleted in the future. Users can still specify the following in-tree plugins in their yaml file. However, behind the scenes, Kubernetes hands control of all storage management operations (previously targeting in-tree drivers) to CSI drivers. -{{< /note >}} +## Types of volumes {#volume-types} +Kubernetes supports several types of volumes. ### awsElasticBlockStore (removed) {#awselasticblockstore} @@ -1109,6 +1103,12 @@ As a result, operators do not have to make any configuration changes to existing Storage Classes, PersistentVolumes or PersistentVolumeClaims (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. +{{< note >}} +* The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. +* Manifests that use in-tree volume plugins will also be used in the future without modifying. +* A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. +{{< /note >}} + The operations and features that are supported include: provisioning/delete, attach/detach, mount/unmount and resizing of volumes. From ceca1bef5339bb647db26059d1935a93fbc53d6b Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Wed, 20 Dec 2023 05:17:42 +0000 Subject: [PATCH 14/19] Deleted the contents that have been stated in the former paragraph --- content/en/docs/concepts/storage/volumes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index d99b29c59b..237608ec2a 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1105,7 +1105,6 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste {{< note >}} * The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. -* Manifests that use in-tree volume plugins will also be used in the future without modifying. * A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. {{< /note >}} From 02ac73e6168d596512a1659e8e4c1d90f14a3978 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Thu, 21 Dec 2023 13:02:09 +0900 Subject: [PATCH 15/19] Update content/en/docs/concepts/storage/volumes.md Co-authored-by: Akihiro Motoki --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 237608ec2a..22fd1e7c35 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1104,7 +1104,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. {{< note >}} -* The existing PV created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed. +* Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. * A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. {{< /note >}} From baeb523426dc3da97b9d28b83821d012bdd618e7 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Thu, 21 Dec 2023 04:28:57 +0000 Subject: [PATCH 16/19] Modified the introduction about new pvs to make it more precise --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 22fd1e7c35..c826469c37 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1105,7 +1105,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste {{< note >}} * Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. -* A new PV with a manifest that uses in-tree volume plugins can still be created, even after the in-tree volume plugin is removed from Kubernetes. +* New PVs with manifests that referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. {{< /note >}} The operations and features that are supported include: From 7fac0e473a6655dec69d0916eea5800738bc0496 Mon Sep 17 00:00:00 2001 From: ziyi-xie Date: Tue, 16 Jan 2024 01:20:14 +0000 Subject: [PATCH 17/19] grammar correction without any modification of the content --- content/en/docs/concepts/storage/volumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index c826469c37..618a1f7d96 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1105,7 +1105,7 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste {{< note >}} * Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. -* New PVs with manifests that referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. +* New PVs in manifests referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. {{< /note >}} The operations and features that are supported include: From a21e5a2573c53ee1765c7d5bae9cb42b91f71331 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Thu, 18 Jan 2024 08:42:32 +0900 Subject: [PATCH 18/19] Update content/en/docs/concepts/storage/volumes.md Co-authored-by: Tim Bannister --- content/en/docs/concepts/storage/volumes.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 618a1f7d96..aa12c706e4 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1104,7 +1104,12 @@ configuration changes to existing Storage Classes, PersistentVolumes or Persiste (referring to in-tree plugins) when transitioning to a CSI driver that supersedes an in-tree plugin. {{< note >}} -* Existing PVs created by in-tree volume plugin can still be used in the future without any configuration changes even after the `CSIMigration` is completed and corresponing in-tree volume plugins are deleted. +Existing PVs created by a in-tree volume plugin can still be used in the future without any configuration +changes, even after the migration to CSI is completed for that volume type, and even after you upgrade to a +version of Kubernetes that doesn't have compiled-in support for that kind of storage. + +As part of that migration, you - or another cluster administrator - **must** have installed and configured +the appropriate CSI driver for that storage. The core of Kubernetes does not install that software for you. * New PVs in manifests referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. {{< /note >}} From 9f62122e758cc83c5535c1ec64f78012cd49ce87 Mon Sep 17 00:00:00 2001 From: ziyi-xie <92832323+ziyi-xie@users.noreply.github.com> Date: Thu, 18 Jan 2024 19:43:57 +0900 Subject: [PATCH 19/19] Update content/en/docs/concepts/storage/volumes.md Co-authored-by: Tim Bannister --- content/en/docs/concepts/storage/volumes.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index aa12c706e4..b7dbf54651 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -1110,7 +1110,14 @@ version of Kubernetes that doesn't have compiled-in support for that kind of sto As part of that migration, you - or another cluster administrator - **must** have installed and configured the appropriate CSI driver for that storage. The core of Kubernetes does not install that software for you. -* New PVs in manifests referring to in-tree volume plugins can still be created, even after the in-tree volume plugins are removed from Kubernetes. + +--- + +After that migration, you can also define new PVCs and PVs that refer to the legacy, built-in +storage integrations. +Provided you have the appropriate CSI driver installed and configured, the PV creation continues +to work, even for brand new volumes. The actual storage management now happens through +the CSI driver. {{< /note >}} The operations and features that are supported include: