openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS 8020 fix a link that used an autogenerated anchor

Browse Source
This commit is contained in:
Misha Ramendik
2023-10-05 00:16:08 +01:00
committed by Kathryn Alexander
parent d685bc5f28
commit aff743a0db
2 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
modules/persistent-storage-csi-migration-vsphere.adoc
View File

@@ -9,6 +9,7 @@
== New installations of {product-title}
For new installations of {product-title} 4.13, or later, automatic migration is enabled by default.
[id="upgrading-openshift_{context}"]
== Upgrading {product-title}
When upgrading from {product-title} 4.12, or earlier, to 4.13, automatic CSI migration for vSphere only occurs if you opt in.

12
storage/container_storage_interface/persistent-storage-csi-vsphere.adoc
View File

@@ -30,7 +30,7 @@ For vSphere:
+
CSI automatic migration should be seamless. Migration does not change how you use all existing API objects, such as persistent volumes, persistent volume claims, and storage classes. For more information about migration, see xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration[CSI automatic migration].
* When upgrading from {product-title} 4.12, or earlier, to 4.13, automatic CSI migration for vSphere only occurs if you opt in. If you do not opt in, {product-title} defaults to using the in-tree (non-CSI) plugin to provision vSphere storage. xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#upgrading-openshift-container-platform[Carefully review the indicated consequences before opting in to migration].
* When upgrading from {product-title} 4.12, or earlier, to 4.13, automatic CSI migration for vSphere only occurs if you opt in. If you do not opt in, {product-title} defaults to using the in-tree (non-CSI) plugin to provision vSphere storage. xref:../../storage/container_storage_interface/persistent-storage-csi-migration.adoc#upgrading-openshift_persistent-storage-csi-migration[Carefully review the indicated consequences before opting in to migration].
After full migration, in-tree plugins will eventually be removed in future versions of {product-title}.
====
@@ -55,14 +55,14 @@ include::modules/persistent-storage-csi-vsphere-install-issues.adoc[leveloffset=
[id="vsphere-pv-encryption"]
== vSphere persistent disks encryption
You can encrypt virtual machines (VMs) and dynamically provisioned persistent volumes (PVs) on {product-title} running on top of vSphere.
You can encrypt virtual machines (VMs) and dynamically provisioned persistent volumes (PVs) on {product-title} running on top of vSphere.
[NOTE]
====
{product-title} does not support RWX-encrypted PVs. You cannot request RWX PVs out of a storage class that uses an encrypted storage policy.
====
You must encrypt VMs before you can encrypt PVs, which you can do during installation or post-installation.
You must encrypt VMs before you can encrypt PVs, which you can do during installation or post-installation.
For information about encrypting VMs, see:
@@ -74,9 +74,9 @@ For information about encrypting VMs, see:
After encrypting VMs, you can configure a storage class that supports dynamic encryption volume provisioning using the vSphere Container Storage Interface (CSI) driver. This can be accomplished in one of two ways using:
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-encryption-datastore-url_persistent-storage-csi-vsphere[Datastore URL]: This approach is not very flexible, and forces you to use a single datastore. It also does not support topology-aware provisioning.
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-encryption-datastore-url_persistent-storage-csi-vsphere[Datastore URL]: This approach is not very flexible, and forces you to use a single datastore. It also does not support topology-aware provisioning.
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-encryption-tag-based_persistent-storage-csi-vsphere[Tag-based placement]: Encrypts the provisioned volumes and uses tag-based placement to target specific datastores.
* xref:../../storage/container_storage_interface/persistent-storage-csi-vsphere.adoc#persistent-storage-csi-vsphere-encryption-tag-based_persistent-storage-csi-vsphere[Tag-based placement]: Encrypts the provisioned volumes and uses tag-based placement to target specific datastores.
include::modules/persistent-storage-csi-vsphere-encryption-datastore-url.adoc[leveloffset=+2]
@@ -103,4 +103,4 @@ include::modules/persistent-storage-csi-vsphere-top-aware-infra-top.adoc[levelof
include::modules/persistent-storage-csi-vsphere-top-aware-results.adoc[leveloffset=+2]
== Additional resources
* xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[Configuring CSI volumes]
* xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[Configuring CSI volumes]