Skip to content

Commit d48932b

Browse files
authored
Merge pull request #65773 from mramendi/fix-link-storage
OSDOCS 8020 fix a link that used an autogenerated anchor
2 parents 6960ee7 + c39bef5 commit d48932b

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@
99
== New installations of {product-title}
1010
For new installations of {product-title} 4.13, or later, automatic migration is enabled by default.
1111

12+
[id="upgrading-openshift_{context}"]
1213
== Upgrading {product-title}
1314
When upgrading from {product-title} 4.12, or earlier, to 4.13, automatic CSI migration for vSphere only occurs if you opt in.
1415

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For vSphere:
3030
+
3131
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].
3232
33-
* 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].
33+
* 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].
3434
3535
After full migration, in-tree plugins will eventually be removed in future versions of {product-title}.
3636
====
@@ -55,14 +55,14 @@ include::modules/persistent-storage-csi-vsphere-install-issues.adoc[leveloffset=
5555
[id="vsphere-pv-encryption"]
5656
== vSphere persistent disks encryption
5757

58-
You can encrypt virtual machines (VMs) and dynamically provisioned persistent volumes (PVs) on {product-title} running on top of vSphere.
58+
You can encrypt virtual machines (VMs) and dynamically provisioned persistent volumes (PVs) on {product-title} running on top of vSphere.
5959

6060
[NOTE]
6161
====
6262
{product-title} does not support RWX-encrypted PVs. You cannot request RWX PVs out of a storage class that uses an encrypted storage policy.
6363
====
6464

65-
You must encrypt VMs before you can encrypt PVs, which you can do during installation or post-installation.
65+
You must encrypt VMs before you can encrypt PVs, which you can do during installation or post-installation.
6666

6767
For information about encrypting VMs, see:
6868

@@ -74,9 +74,9 @@ For information about encrypting VMs, see:
7474

7575
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:
7676

77-
* 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.
77+
* 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.
7878

79-
* 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.
79+
* 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.
8080

8181
include::modules/persistent-storage-csi-vsphere-encryption-datastore-url.adoc[leveloffset=+2]
8282

@@ -103,4 +103,4 @@ include::modules/persistent-storage-csi-vsphere-top-aware-infra-top.adoc[levelof
103103
include::modules/persistent-storage-csi-vsphere-top-aware-results.adoc[leveloffset=+2]
104104

105105
== Additional resources
106-
* xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[Configuring CSI volumes]
106+
* xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[Configuring CSI volumes]

0 commit comments

Comments
 (0)