Skip to content

Commit 21b0105

Browse files
authored
Merge pull request #45025 from lpettyjo/OSDOCS-3544and3545
OSDOCS-3544 & 3545: CSI Migration of Cinder and Azure Disk to GA
2 parents e05a5ee + 278e883 commit 21b0105

5 files changed

+102
-26
lines changed
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * storage/container_storage_interface/persistent-storage-csi-migration.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="persistent-storage-csi-migration-automatic-ga_{context}"]
7+
= Automatic migration of in-tree volumes to CSI
8+
9+
{product-title} supports automatic and seamless migration for the following in-tree volume types to their Container Storage Interface (CSI) driver counterpart:
10+
11+
* Azure Disk
12+
13+
* OpenStack Cinder
14+
15+
CSI migration for these volume types is considered generally available (GA), and requires no manual intervention.
16+
17+
For new {product-title} 4.11, and later, installations, the default storage class is the CSI storage class. All volumes provisioned using this storage class are CSI persistent volumes (PVs).
18+
19+
For clusters upgraded from 4.10, and earlier, to 4.11, and later, the CSI storage class is created, and is set as the default if no default storage class was set prior to the upgrade. In the very unlikely case that there is a storage class with the same name, the existing storage class remains unchanged. Any existing in-tree storage classes remain, and might be necessary for certain features, such as volume expansion to work for existing in-tree PVs. While storage class referencing to the in-tree storage plug-in will continue working, we recommend that you switch the default storage class to the CSI storage class.

modules/persistent-storage-csi-migration-enable.adoc

Lines changed: 20 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,24 @@
44

55
:_content-type: PROCEDURE
66
[id="persistent-storage-csi-migration-enable_{context}"]
7-
= Enabling CSI automatic migration
7+
= Manually enabling CSI automatic migration
8+
9+
If you want to test Container Storage Interface (CSI) migration in development or staging {product-title} clusters, you must manually enable in-tree to CSI migration for the following in-tree volume types:
10+
11+
* AWS Elastic Block Storage (EBS)
12+
13+
* Google Compute Engine Persistent Disk (GCE-PD)
14+
15+
* VMware vSphere Disk
16+
17+
* Azure File
18+
19+
:FeatureName: CSI automatic migration for the preceding in-tree volume plug-ins and CSI driver pairs
20+
include::snippets/technology-preview.adoc[leveloffset=+1]
21+
22+
After migration, the default storage class remains the in-tree storage class.
23+
24+
CSI automatic migration will be enabled by default for all storage in-tree plug-ins in a future {product-title} release, so it is highly recommended that you test it now and report any issues.
825

926
[NOTE]
1027
====
@@ -20,7 +37,7 @@ Enabling CSI automatic migration drains, and then restarts, all nodes in the clu
2037
After turning on Technology Preview features using feature gates, they cannot be turned off. As a result, cluster upgrades are prevented.
2138
====
2239
+
23-
The following configuration example enables CSI automatic migration to all CSI drivers supported by this feature:
40+
The following configuration example enables CSI automatic migration for all CSI drivers supported by this feature that are currently in Technology Preview (TP) status:
2441
+
2542
[source,yaml]
2643
----
@@ -32,17 +49,13 @@ spec:
3249
featureSet: TechPreviewNoUpgrade <1>
3350
...
3451
----
35-
<1> Enables automatic migration for AWS EBS, Cinder, GCP, Azure Disk, Azure File, and VMware vSphere.
52+
<1> Enables automatic migration for AWS EBS, GCP, Azure File, and VMware vSphere.
3653
+
3754
You can specify CSI automatic migration for a selected CSI driver by setting `CustomNoUpgrade` `featureSet` and for `featuregates` to one of the following:
3855
+
3956
--
4057
* CSIMigrationAWS
4158
42-
* CSIMigrationOpenStack
43-
44-
* CSIMigrationAzure
45-
4659
* CSIMigrationAzureFile
4760
4861
* CSIMigrationGCE
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * storage/container_storage_interface/persistent-storage-csi-migration.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="persistent-storage-csi-migration-overview-support-level_{context}"]
7+
= Automatic migration support level
8+
9+
Certain in-tree volume plug-ins and their equivalent Container Storage Interface (CSI) driver are supported in Technology Preview (TP) status, whereas others are supported in General Availability (GA) status.
10+
11+
The following table provides details about the support level of in-tree volume plug-ins/CSI driver pairs.
12+
13+
.CSI automatic migration In-tree volume plug-ins/CSI driver pair support in {product-title}
14+
[cols=",^v,^v,^v width="100%",options="header"]
15+
|===
16+
|CSI drivers |Support level |CSI auto migration enabled automatically?
17+
18+
a|
19+
* Amazon Web Services (AWS) Elastic Block Storage (EBS)
20+
* Azure File
21+
* Google Compute Engine Persistent Disk (in-tree) and Google Cloud Platform Persistent Disk (CSI)
22+
* VMware vSphere
23+
|TP
24+
| No. To enable, see "_Enabling CSI automatic migration_".
25+
26+
a|
27+
* Azure Disk
28+
* OpenStack Cinder
29+
|GA
30+
| Yes
31+
|===
32+
33+
[IMPORTANT]
34+
====
35+
CSI automatic migration will be enabled by default for all storage in-tree plug-ins in a future {product-title} release, so it is highly recommended that you test it now and report any issues.
36+
====

modules/persistent-storage-csi-migration-overview.adoc

Lines changed: 17 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,27 +6,30 @@
66
[id="persistent-storage-csi-migration-overview_{context}"]
77
= Overview
88

9-
With the automatic migration feature enabled, volumes provisioned using in-tree storage plug-ins supported by this feature are migrated to their counterpart CSI drivers.
9+
Volumes that are provisioned by using in-tree storage plug-ins, and that are supported by this feature, are migrated to their counterpart Container Storage Interface (CSI) drivers. This process does not perform any data migration; {product-title} only translates the persistent volume object in memory. As a result, the translated persistent volume object is not stored on disk, nor is its contents changed.
1010

11-
The following drivers are supported:
11+
The following in-tree to CSI drivers are supported:
1212

13-
* Amazon Web Services (AWS) Elastic Block Storage (EBS)
14-
15-
* OpenStack Cinder
13+
.CSI automatic migration feature supported in-tree/CSI drivers
14+
[cols=",^v,^v,^v width="100%",options="header"]
15+
|===
16+
|In-tree/CSI drivers |Support level |CSI auto migration enabled automatically?
1617

18+
a|
1719
* Azure Disk
20+
* OpenStack Cinder
21+
|Generally available (GA)
22+
| Yes. For more information, see "_Automatic migration of in-tree volumes to CSI_".
1823

24+
a|
25+
* Amazon Web Services (AWS) Elastic Block Storage (EBS)
1926
* Azure File
20-
2127
* Google Compute Engine Persistent Disk (in-tree) and Google Cloud Platform Persistent Disk (CSI)
22-
2328
* VMware vSphere
29+
|Techology Preview (TP)
30+
| No. To enable, see "_Manually enabling CSI automatic migration_".
31+
|===
2432

25-
CSI automatic migration should be seamless. Enabling this feature does not change how you use all existing API objects (for example, `PersistentVolumes`, `PersistentVolumeClaims`, and `StorageClasses`).
26-
27-
By default, automatic migration is disabled.
33+
CSI automatic migration should be seamless. This feature does not change how you use all existing API objects: for example, `PersistentVolumes`, `PersistentVolumeClaims`, and `StorageClasses`.
2834

29-
[IMPORTANT]
30-
====
31-
CSI automatic migration will be enabled by default in a future {product-title} release, so it is highly recommended that you test it now and report any issues.
32-
====
35+
Enabling CSI automatic migration for in-tree persistent volumes (PVs) or persistent volume claims (PVCs) does not enable any new CSI driver features, such as snapshots or expansion, if the original in-tree storage plug-in did not support it.

storage/container_storage_interface/persistent-storage-csi-migration.adoc

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,21 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
{product-title} provides automatic migration for supported in-tree volume plug-ins to their equivalent Container Storage Interface (CSI) drivers.
10-
11-
:FeatureName: CSI automatic migration
12-
include::snippets/technology-preview.adoc[leveloffset=+1]
9+
In-tree storage drivers that are traditionally shipped with {product-title} are being deprecated and replaced by their equivalent Container Storage Interface (CSI) drivers. {product-title} provides automatic migration for certain supported in-tree volume plug-ins to their equivalent CSI drivers.
1310

1411
include::modules/persistent-storage-csi-migration-overview.adoc[leveloffset=+1]
1512

13+
[role="_additional-resources"]
14+
.Additional resources
15+
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-automatic-ga_persistent-storage-csi-migration[Automatic migration of in-tree volumes to CSI]
16+
17+
* xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration-enable_persistent-storage-csi-migration[Manually enabling CSI automatic migration]
18+
19+
include::modules/persistent-storage-csi-migration-automatic-ga.adoc[leveloffset=+1]
20+
1621
include::modules/persistent-storage-csi-migration-enable.adoc[leveloffset=+1]
1722

1823
[role="_additional-resources"]
19-
== Additional resources
24+
.Additional resources
2025

2126
* xref:../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[Enabling features using feature gates]

0 commit comments

Comments
 (0)