MTV-3225: Replacing links that contain attributes

RichardHoch · RichardHoch · commit 937022356dc4 · 2025-09-07T15:03:51.000+03:00
diff --git a/documentation/modules/accessing-logs-cli.adoc b/documentation/modules/accessing-logs-cli.adoc
@@ -18,7 +18,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/cli_tools/openshift-cli-oc#cli-getting-started[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short}].
 
 .Procedure
 
diff --git a/documentation/modules/adding-hook-using-cli.adoc b/documentation/modules/adding-hook-using-cli.adoc
@@ -30,7 +30,7 @@ You can retrieve additional information stored in a secret or in a `ConfigMap` b
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 . If needed, create a Secret with an SSH private key for the VM.
diff --git a/documentation/modules/adding-hook-using-ui.adoc b/documentation/modules/adding-hook-using-ui.adoc
@@ -25,7 +25,7 @@ You can run one pre-migration hook, one post-migration hook, or one of each per
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 
diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc
@@ -78,7 +78,7 @@ You can migrate VMs from the cluster that {project-short} is deployed on to anot
 
 .Prerequisites
 
-* You must have {a-virt} link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/authentication_and_authorization/using-service-accounts[service account token] with `cluster-admin` privileges.
+* You must have {a-virt} service account token with `cluster-admin` privileges. For more information on service account tokens, see {ocp-doc}/authentication_and_authorization/using-service-accounts#service-accounts-overview_using-service-accounts[Service accounts overview].
 endif::[]
 
 .Procedure
diff --git a/documentation/modules/common-attributes.adoc b/documentation/modules/common-attributes.adoc
@@ -11,6 +11,7 @@
 // when updating the ocp-version, update the ocp-y-version
 :ocp-version: 4.19
 :ocp-y-version: 4.19, 4.18, 4.17
+:ocp-doc: link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single
 :operator: mtv-operator
 :operator-name-ui: Migration Toolkit for Virtualization Operator
 :operator-name: MTV Operator
diff --git a/documentation/modules/creating-plan-wizard-290-cnv.adoc b/documentation/modules/creating-plan-wizard-290-cnv.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-ostack.adoc b/documentation/modules/creating-plan-wizard-290-ostack.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-ova.adoc b/documentation/modules/creating-plan-wizard-290-ova.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-rhv.adoc b/documentation/modules/creating-plan-wizard-290-rhv.adoc
@@ -123,7 +123,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-vmware.adoc b/documentation/modules/creating-plan-wizard-290-vmware.adoc
@@ -130,7 +130,7 @@ You do not need to enter the passphrases in a specific order. For each LUKS-encr
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-vddk-image.adoc b/documentation/modules/creating-vddk-image.adoc
@@ -24,7 +24,7 @@ Storing the VDDK image in a public registry might violate the VMware license ter
 
 .Prerequisites
 
-* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[{ocp} image registry].
+* {ocp-doc}/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[{ocp} image registry].
 * `podman` installed.
 * You are working on a file system that preserves symbolic links (symlinks).
 * If you are using an external registry, {virt} must be able to access it.
@@ -41,11 +41,6 @@ $ mkdir /tmp/<dir_name> && cd /tmp/<dir_name>
 . In a browser, navigate to the link:https://developer.vmware.com/web/sdk/8.0/vddk[VMware VDDK version 8 download page].
 . Select version 8.0.1 and click *Download*.
 
-[NOTE]
-====
-In order to migrate to {virt} 4.12, download VDDK version 7.0.3.2 from the link:https://developer.vmware.com/web/sdk/7.0/vddk[VMware VDDK version 7 download page].
-====
-
 . Save the VDDK archive file in the temporary directory.
 . Extract the VDDK archive:
 +
diff --git a/documentation/modules/network-prerequisites.adoc b/documentation/modules/network-prerequisites.adoc
@@ -10,7 +10,7 @@ The following prerequisites apply to all migrations:
 
 * IP addresses, VLANs, and other network configuration settings must not be changed before or during migration. The MAC addresses of the virtual machines are preserved during migration.
 * The network connections between the source environment, the {virt} cluster, and the replication repository must be reliable and uninterrupted.
-* If you are mapping more than one source and destination network, you must create a link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/virtualization/virtual-machines#virt-creating-network-attachment-definition[network attachment definition] for each additional destination network.
+* If you are mapping more than one source and destination network, you must create a network attachment definition for each additional destination network. For more information, see {ocp-doc}/virtualization/index#virt-creating-vms-from-rh-images-overview[Creating virtual machines from Red Hat images overview].
 
 [id="ports_{context}"]
 == Ports
diff --git a/documentation/modules/storage-support.adoc b/documentation/modules/storage-support.adoc
@@ -60,7 +60,7 @@
 
 [NOTE]
 ====
-If the {virt} storage does not support link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/dynamic-provisioning[dynamic provisioning], you must apply the following settings:
+If the {virt} storage does not support {ocp-doc}/storage/dynamic-provisioning#dynamic-provisioning[dynamic provisioning], you must apply the following settings:
 
 * `Filesystem` volume mode
 +
diff --git a/documentation/modules/upgrading-mtv-ui.adoc b/documentation/modules/upgrading-mtv-ui.adoc
@@ -14,10 +14,10 @@ You can upgrade the {operator-name} by using the {ocp} web console to install th
 . Change the update channel to the correct release.
 +
 ifeval::["{build}" == "upstream"]
-See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing the manual update channel for an Operator] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
 endif::[]
 
 . Confirm that *Upgrade status* changes from *Up to date* to *Upgrade available*. If it does not, restart the `CatalogSource` pod:
@@ -47,9 +47,5 @@ ifeval::["{build}" == "upstream"]
 See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
 endif::[]
-
-. If you are upgrading from {project-short} 2.2 and have defined VMware source providers, edit the VMware provider by adding a VDDK `init` image. Otherwise, the update will change the state of any VMware providers to `Critical`. For more information, see link:https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/migrating-vms-web-console#adding-source-provider_vmware[Adding a VMSphere source provider].
-
-. If you mapped to NFS on the {ocp} destination provider in {project-short} 2.2, edit the `AccessModes` and `VolumeMode` parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/virtualization/index#virt-customizing-storage-profile_virt-creating-data-volumes[Customizing the storage profile].
diff --git a/documentation/modules/using-must-gather.adoc b/documentation/modules/using-must-gather.adoc
@@ -17,7 +17,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://docs.openshift.com/container-platform/{ocp-version}/cli_reference/openshift_cli/getting-started-cli.html[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short}].
 
 .Collecting logs and CR information
 
diff --git a/documentation/modules/vddk-validator-containers.adoc b/documentation/modules/vddk-validator-containers.adoc
@@ -4,39 +4,47 @@
 
 :_content-type: REFERENCE
 [id="vddk-validator-containers_{context}"]
-= VDDK validator containers need requests and limits
+= Requests and limits for VDDK validator containers 
 
-If you have the link:https://docs.openshift.com/container-platform/{ocp-version}/applications/quotas/quotas-setting-per-project.html[cluster or project resource quotas set], you must ensure that you have a sufficient quota for the {project-short} pods to perform the migration. 
+When you set cluster or project resource quotas, be sure that you have a sufficient quota for the {project-short} pods to perform the migration. 
 
-You can see the defaults, which you can override in the ForkliftController custom resource (CR), listed as follows. If necessary, you can adjust these defaults. 
+For more information on creating, setting, and viewing quotas, see {ocp-doc}/building_applications/index#quotas[Quotas]
 
-These settings are highly dependent on your environment. If there are many migrations happening at once and the quotas are not set enough for the migrations, then the migrations can fail. This can also be correlated to the `MAX_VM_INFLIGHT` setting that determines how many VMs/disks are migrated at once.
+The defaults that are related to VDDK validator containers are listed as follows. You can override these defaults in the `ForkliftController` custom resource (CR).
 
-.Defaults which can be overriden in the ForkliftController CR:
 
-* This affects both cold and warm migrations:
+[NOTE]
+====
+These settings are highly dependent on your environment. If there are many migrations happening at once and the quotas are not set high enough for the migrations, then the migrations can fail. 
+
+Migration success or failure is also connected to the `MAX_VM_INFLIGHT` setting that determines how many VMs or disks are migrated at once.
+====
+
+[id="defaults-that-can-be-overridden-in-forklift-controller_{context}"]
+== Defaults that can be overridden in the ForkliftController CR:
+
+* These defaults affect both cold and warm migrations:
 +
-For cold migration, it is likely to be more resource intensive as it performs the disk copy. For warm migration, you could potentially reduce the requests.
+Cold migration is likely to be more resource intensive because it copies the disks. For warm migration, you could potentially reduce the requests.
 
 ** virt_v2v_container_limits_cpu: `4000m`
 ** virt_v2v_container_limits_memory: `8Gi`
 ** virt_v2v_container_requests_cpu: `1000m`
 ** virt_v2v_container_requests_memory: `1Gi`
 +
-
 [NOTE]
 ====
 Cold and warm migration using `virt-v2v` can be resource-intensive. For more details, see link:https://libguestfs.org/virt-v2v.1.html#compute-power-and-ram[Compute power and RAM].
 ====
 
+* These defaults affect all migrations with hooks:
 
-* This affects any migrations with hooks:
 ** hooks_container_limits_cpu: `1000m`
 ** hooks_container_limits_memory: `1Gi`
 ** hooks_container_requests_cpu: `100m`
 ** hooks_container_requests_memory: `150Mi`
 
-* This affects any OVA migrations:
+* TThese defaults affect all Open Virtual Appliance (OVA) file migrations: migrations:
 
 ** ova_container_limits_cpu: `1000m`
 ** ova_container_limits_memory: `1Gi`
diff --git a/documentation/modules/virt-migration-workflow.adoc b/documentation/modules/virt-migration-workflow.adoc
@@ -25,7 +25,7 @@ The workflow describes the following steps:
 +
 *For each VM disk:*
 
-. The `Containerized Data Importer (CDI) Controller` service creates a persistent volume claim (PVC) based on the parameters specified in the `DataVolume` CR.  
+. The `Containerized Data Importer (CDI) Controller` service creates a persistent volume claim (PVC) based on the parameters specified in the `DataVolume` CR.
 . If the `StorageClass` has a dynamic provisioner, the persistent volume (PV) is dynamically provisioned by the `StorageClass` provisioner.
 . The `CDI Controller` service creates an `importer` pod.
 . The `importer` pod streams the VM disk to the PV.
@@ -67,7 +67,7 @@ The `virt-launcher` pod runs `QEMU-KVM` with the PVCs attached as VM disks.
 +
 *For each VM disk:*
 
-. The `Containerized Data Importer (CDI) Controller` service creates a blank persistent volume claim (PVC) based on the parameters specified in the `DataVolume` CR.  
+. The `Containerized Data Importer (CDI) Controller` service creates a blank persistent volume claim (PVC) based on the parameters specified in the `DataVolume` CR.
 . If the `StorageClass` has a dynamic provisioner, the persistent volume (PV) is dynamically provisioned by the `StorageClass` provisioner.
 
 *For all VM disks:*

Original file line number	Diff line number	Diff line change
`@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is`
`114`	`114`	`** To choose a different transfer network, select a different transfer network from the list.`
`115`	`115`	`** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.`
`116`	`116`	`+`
`117`		`-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].`
	`117`	`+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].`
`118`	`118`
`119`	`119`	`** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].`
`120`	`120`
Original file line number	Diff line number	Diff line change
`@@ -123,7 +123,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is`
`123`	`123`	`** To choose a different transfer network, select a different transfer network from the list.`
`124`	`124`	`** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.`
`125`	`125`	`+`
`126`		`-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].`
	`126`	`+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].`
`127`	`127`
`128`	`128`	`** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].`
`129`	`129`
Original file line number	Diff line number	Diff line change
`@@ -130,7 +130,7 @@ You do not need to enter the passphrases in a specific order. For each LUKS-encr`
`130`	`130`	`** To choose a different transfer network, select a different transfer network from the list.`
`131`	`131`	`** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.`
`132`	`132`	`+`
`133`		`-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].`
	`133`	`+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].`
`134`	`134`
`135`	`135`	`** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].`
`136`	`136`