Fixing broken links on portal docs

adellape · Apr 6, 2022 · 4fa0f0f · 4fa0f0f
1 parent 50ad5d6
commit 4fa0f0f
Show file tree

Hide file tree

Showing 43 changed files with 84 additions and 84 deletions.
diff --git a/installing/installing_ibm_power/installing-ibm-power.adoc b/installing/installing_ibm_power/installing-ibm-power.adoc
@@ -49,7 +49,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc b/installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc
@@ -57,7 +57,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_ibm_z/installing-ibm-z-kvm.adoc b/installing/installing_ibm_z/installing-ibm-z-kvm.adoc
@@ -52,7 +52,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [id="additional-resources_ibmz-kvm-chrony-time-service"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_ibm_z/installing-ibm-z.adoc b/installing/installing_ibm_z/installing-ibm-z.adoc
@@ -68,7 +68,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [id="additional-resources_ibmz-chrony-time-service"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc b/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc
@@ -60,7 +60,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [id="additional-resources_ibmz-network-user-infra"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc b/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc
@@ -74,7 +74,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_platform_agnostic/installing-platform-agnostic.adoc b/installing/installing_platform_agnostic/installing-platform-agnostic.adoc
@@ -44,7 +44,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_vsphere/installing-restricted-networks-vsphere.adoc b/installing/installing_vsphere/installing-restricted-networks-vsphere.adoc
@@ -66,7 +66,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_vsphere/installing-vsphere-network-customizations.adoc b/installing/installing_vsphere/installing-vsphere-network-customizations.adoc
@@ -58,7 +58,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/installing/installing_vsphere/installing-vsphere.adoc b/installing/installing_vsphere/installing-vsphere.adoc
@@ -57,7 +57,7 @@ include::modules/installation-network-user-infra.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
+* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
 
 include::modules/installation-dns-user-infra.adoc[leveloffset=+2]
 

diff --git a/modules/images-imagestream-import-images-private-registry.adoc b/modules/images-imagestream-import-images-private-registry.adoc
@@ -5,7 +5,7 @@
 [id="images-imagestream-import-images-private-registry_{context}"]
 = Importing images and image streams from private registries
 
-An image stream can be configured to import tag and image metadata from private image registries requiring authentication. This procedures applies if you change the registry that the Cluster Samples Operator uses to pull content from to something other than link:registry.redhat.io[registry.redhat.io].
+An image stream can be configured to import tag and image metadata from private image registries requiring authentication. This procedures applies if you change the registry that the Cluster Samples Operator uses to pull content from to something other than link:https://registry.redhat.io[registry.redhat.io].
 
 [NOTE]
 ====

diff --git a/modules/images-other-jenkins-agent-images.adoc b/modules/images-other-jenkins-agent-images.adoc
@@ -5,7 +5,7 @@
 [id="images-other-jenkins-agent-images_{context}"]
 = Jenkins agent images
 
-The {product-title} Jenkins agent images are available on link:quay.io[Quay.io] or link:registry.redhat.io[registry.redhat.io].
+The {product-title} Jenkins agent images are available on link:https://quay.io[Quay.io] or link:https://registry.redhat.io[registry.redhat.io].
 
 Jenkins images are available through the Red Hat Registry:
 
@@ -34,4 +34,4 @@ $ docker pull registry.redhat.io/openshift4/ose-jenkins-agent-maven:<v4.5.0>
 $ docker pull registry.redhat.io/openshift4/ose-jenkins-agent-base:<v4.5.0>
 ----
 
-To use these images, you can either access them directly from link:quay.io[Quay.io] or link:registry.redhat.io[registry.redhat.io]` or push them into your {product-title} container image registry.
+To use these images, you can either access them directly from link:https://quay.io[Quay.io] or link:https://registry.redhat.io[registry.redhat.io] or push them into your {product-title} container image registry.
diff --git a/modules/installation-osp-control-compute-machines.adoc b/modules/installation-osp-control-compute-machines.adoc
@@ -33,7 +33,7 @@ run as many as you can.
 ====
 
 ifdef::osp-sr-iov[]
-Additionally, for clusters that use single-root input/output virtualization (SR-IOV), {rh-openstack} compute nodes require a flavor that supports link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/configuring_the_compute_service_for_instance_creation/configuring-compute-nodes-for-performance#configuring-huge-pages-on-compute-nodes-osp[huge pages].
+Additionally, for clusters that use single-root input/output virtualization (SR-IOV), {rh-openstack} compute nodes require a flavor that supports link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/configuring_the_compute_service_for_instance_creation/assembly_configuring-compute-nodes-for-performance_compute-performance#proc_configuring-huge-pages-on-compute-nodes_compute-performance[huge pages].
 
 [IMPORTANT]
 ====
@@ -54,4 +54,4 @@ ifeval::["{context}" == "installing-openstack-installer-sr-iov"]
 endif::[]
 ifeval::["{context}" == "installing-openstack-installer-ovs-dpdk"]
 :!osp-sr-iov:
-endif::[]
+endif::[]
diff --git a/modules/installation-osp-provider-network-preparation.adoc b/modules/installation-osp-provider-network-preparation.adoc
@@ -10,8 +10,8 @@
 
 Before you install an {product-title} cluster, your {rh-openstack-first} deployment and provider network must meet a number of conditions:
 
-* The link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-concepts_networking-concepts#install-networking_networking-concepts[{rh-openstack} networking service (Neutron) is enabled] and accessible through the {rh-openstack} networking API.
-* The {rh-openstack} networking service has the link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/config-allowed-address-pairs_config-allowed-address-pairs#overview-allow-addr-pairs_config-allowed-address-pairs[port security and allowed address pairs extensions enabled].
+* The link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-overview_rhosp-network#install-networking_network-overview[{rh-openstack} networking service (Neutron) is enabled] and accessible through the {rh-openstack} networking API.
+* The {rh-openstack} networking service has the link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/config-allowed-address-pairs_rhosp-network#overview-allow-addr-pairs_config-allowed-address-pairs[port security and allowed address pairs extensions enabled].
 * The provider network can be shared with other tenants.
 +
 [TIP]
@@ -34,7 +34,7 @@ To create a subnet for a project that is named "openshift," enter the following
 $ openstack subnet create --project openshift
 ----
 
-To learn more about creating networks on {rh-openstack}, read link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-concepts_networking-concepts#tenant-provider-networks_networking-concepts[the provider networks documentation].
+To learn more about creating networks on {rh-openstack}, read link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-overview_rhosp-network#tenant-provider-networks_network-overview[the provider networks documentation].
 ====
 +
 If the cluster is owned by the `admin` user, you must run the installer as that user to create ports on the network.
@@ -53,4 +53,4 @@ Depending on your {rh-openstack} SDN and networking service configuration, you m
 $ openstack subnet create --dhcp --host-route destination=169.254.169.254/32,gateway=192.0.2.2 ...
 ----
 
-* Optional: To secure the network, create link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/config-rbac-policies_config-rbac-policies[role-based access control (RBAC)] rules that limit network access to a single project.
+* Optional: To secure the network, create link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/config-rbac-policies_rhosp-network#proc_create-rbac-policies_config-rbac-policies[role-based access control (RBAC)] rules that limit network access to a single project.
diff --git a/modules/installation-osp-provider-networks.adoc b/modules/installation-osp-provider-networks.adoc
@@ -25,4 +25,4 @@ Example provider network types include flat (untagged) and VLAN (802.1Q tagged).
 A cluster can support as many provider network connections as the network type allows. For example, VLAN networks typically support up to 4096 connections.
 ====
 
-You can learn more about provider and tenant networks in link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-concepts_networking-concepts#provider-networks_networking-concepts[the {rh-openstack} documentation].
+You can learn more about provider and tenant networks in link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_guide/networking-overview_rhosp-network#tenant-provider-networks_network-overview[the {rh-openstack} documentation].
diff --git a/modules/installation-osp-setting-worker-affinity.adoc b/modules/installation-osp-setting-worker-affinity.adoc
@@ -14,11 +14,11 @@
 
 Optionally, you can set the affinity policy for compute machines during installation. By default, both compute and control plane machines are created with a `soft-anti-affinity` policy.
 
-You can also create machine sets that use particular {rh-openstack} server groups after installation. 
+You can also create machine sets that use particular {rh-openstack} server groups after installation.
 
 [TIP]
 ====
-You can learn more about link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/configuring_the_compute_service_for_instance_creation/configuring-instance-scheduling-and-placement[{rh-openstack} instance scheduling and placement] in the {rh-openstack} documentation.
+You can learn more about link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/configuring_the_compute_service_for_instance_creation/assembly_configuring-instance-scheduling-and-placement_scheduling-and-placement[{rh-openstack} instance scheduling and placement] in the {rh-openstack} documentation.
 ====
 
 .Prerequisites
@@ -114,4 +114,4 @@ spec:
 
 . Optional: Back up the `manifests/99_openshift-cluster-api_worker-machineset-0.yaml` file. The installation program deletes the `manifests/` directory when creating the cluster.
 
-When you install the cluster, the installer uses the `MachineSet` definition that you modified to create compute machines within your {rh-openstack} server group. 
+When you install the cluster, the installer uses the `MachineSet` definition that you modified to create compute machines within your {rh-openstack} server group.
diff --git a/modules/nw-egress-router-about.adoc b/modules/nw-egress-router-about.adoc
@@ -101,7 +101,7 @@ $ openstack port set --allowed-address \
 
 {rh-virtualization-first}::
 
-If you are using link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/sect-virtual_network_interface_cards#Explanation_of_Settings_in_the_VM_Interface_Profile_Window[{rh-virtualization}], you must select *No Network Filter* for the Virtual network interface controller (vNIC).
+If you are using link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/chap-logical_networks#Explanation_of_Settings_in_the_VM_Interface_Profile_Window[{rh-virtualization}], you must select *No Network Filter* for the Virtual network interface controller (vNIC).
 
 VMware vSphere::
 

diff --git a/modules/persistent-storage-csi-cinder-storage-class.adoc b/modules/persistent-storage-csi-cinder-storage-class.adoc
@@ -9,9 +9,9 @@ The OpenStack Cinder CSI driver uses the `cinder.csi.openstack.org` parameter ke
 
 To enable OpenStack Cinder CSI provisioning in {product-title}, it is recommended that you overwrite the default in-tree storage class with `standard-csi`. Alternatively, you can create the persistent volume claim (PVC) and specify the storage class as "standard-csi".
 
-In {product-title}, the default storage class references the in-tree Cinder driver. However, with xref:../container_storage_interface/persistent-storage-csi-migration.adoc#persistent-storage-csi-migration[CSI automatic migration] enabled, volumes created using the default storage class actually use the CSI driver.
+In {product-title}, the default storage class references the in-tree Cinder driver. However, with CSI automatic migration enabled, volumes created using the default storage class actually use the CSI driver.
 
-.Recommended procedure
+.Procedure
 Use the following steps to apply the `standard-csi` storage class by overwriting the default in-tree storage class.
 
 . List the storage class:

diff --git a/modules/storage-create-storage-class.adoc b/modules/storage-create-storage-class.adoc
@@ -39,7 +39,7 @@ endif::[]
 ifeval::["{Provisioner}" == "kubernetes.io/aws-ebs"]
 [NOTE]
 ====
-To create the storage class with the equivalent CSI driver, select `{CsiDriver}` from the drop-down list. For more details, see xref:../persistent_storage/persistent-storage-aws.adoc#additional-resources[Additional resources].
+To create the storage class with the equivalent CSI driver, select `{CsiDriver}` from the drop-down list. For more details, see _AWS Elastic Block Store CSI Driver Operator_.
 ====
 endif::[]
 

diff --git a/monitoring/osd-understanding-the-monitoring-stack.adoc b/monitoring/osd-understanding-the-monitoring-stack.adoc
@@ -23,8 +23,8 @@ include::modules/osd-monitoring-targets-for-user-defined-projects.adoc[leveloffs
 == Additional resources
 
 * xref:../monitoring/osd-accessing-monitoring-for-user-defined-projects.adoc#osd-accessing-monitoring-for-user-defined-projects[Accessing monitoring for user-defined projects]
-* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/monitoring/understanding-the-monitoring-stack#default-monitoring-components_understanding-the-monitoring-stack[Default monitoring components]
-* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/monitoring/understanding-the-monitoring-stack#default-monitoring-targets_understanding-the-monitoring-stack[Default monitoring targets]
+* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/monitoring/monitoring-overview#default-monitoring-components_monitoring-overview[Default monitoring components]
+* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/monitoring/monitoring-overview#default-monitoring-targets_monitoring-overview[Default monitoring targets]
 // TODO: When there is a link to the OCP docs, should that be explicit, so they're not surprised when they find themselves in another doc set?
 
 [id="understanding-the-monitoring-stack-next-steps"]

diff --git a/openshift_images/using_images/images-other-jenkins.adoc b/openshift_images/using_images/images-other-jenkins.adoc
@@ -12,7 +12,7 @@ The image is based on the Red Hat Universal Base Images (UBI).
 
 {product-title} follows the link:https://jenkins.io/changelog-stable/[LTS] release of Jenkins. {product-title} provides an image that contains Jenkins 2.x.
 
-The {product-title} Jenkins images are available on link:quay.io[Quay.io] or link:registry.redhat.io[registry.redhat.io].
+The {product-title} Jenkins images are available on link:https://quay.io[Quay.io] or link:https://registry.redhat.io[registry.redhat.io].
 
 For example:
 

diff --git a/rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-peering.adoc b/rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-peering.adoc
@@ -20,7 +20,7 @@ ifdef::openshift-dedicated[]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../cloud_infrastructure_access/dedicated-aws-access.adoc#dedicated-aws-ocm-iam-role[Logging into the Web Console for the AWS Account]
+* xref:../../rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-access.adoc#dedicated-aws-ocm-iam-role[Logging into the Web Console for the AWS Account]
 endif::[]
 
 include::modules/dedicated-aws-vpc-accepting-peering.adoc[leveloffset=+1]