From ee7bd7af993fdad88e274b8b6193ac1883fdda77 Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Thu, 23 Sep 2021 11:49:59 -0400 Subject: [PATCH] Fix broken external links --- modules/creating-the-vsphere-windows-vm-golden-image.adoc | 2 +- modules/deploy-red-hat-openshift-container-storage.adoc | 2 +- .../installation-osp-deploying-bare-metal-machines.adoc | 2 +- modules/migrating-reconcile-code.adoc | 6 +++--- modules/rhel-compute-available-hooks.adoc | 8 ++++---- modules/security-platform-authentication.adoc | 2 +- modules/virt-about-red-hat-ansible-automation.adoc | 2 +- storage/persistent_storage/persistent-storage-iscsi.adoc | 2 +- storage/persistent_storage/persistent-storage-ocs.adoc | 4 ++-- .../understanding-windows-container-workloads.adoc | 2 +- 10 files changed, 16 insertions(+), 16 deletions(-) diff --git a/modules/creating-the-vsphere-windows-vm-golden-image.adoc b/modules/creating-the-vsphere-windows-vm-golden-image.adoc index 68c387ad17..af1796f17a 100644 --- a/modules/creating-the-vsphere-windows-vm-golden-image.adoc +++ b/modules/creating-the-vsphere-windows-vm-golden-image.adoc @@ -65,7 +65,7 @@ This entry ensures the following: . Pull all of the required Windows container base images needed for your applications. The images you pull are dependent on the Windows kernel you are using. See Microsoft's documentation on link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-base-images[pulling Windows container base images] for more information. -. Run the link:https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation[Windows Sysprep tool] on the Windows VM: +. Run the link:+++https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation+++[Windows Sysprep tool] on the Windows VM: + [source,terminal] ---- diff --git a/modules/deploy-red-hat-openshift-container-storage.adoc b/modules/deploy-red-hat-openshift-container-storage.adoc index a304ce6b90..9b0d6d1efa 100644 --- a/modules/deploy-red-hat-openshift-container-storage.adoc +++ b/modules/deploy-red-hat-openshift-container-storage.adoc @@ -45,6 +45,6 @@ |link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html/troubleshooting_openshift_container_storage/index[Troubleshooting OpenShift Container Storage 4.5] |Migrating your {product-title} cluster from version 3 to version 4 -|link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/migrating_from_ocp_3_to_4/index[Migration] +|link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/migrating_from_version_3_to_4/index[Migration] |=== diff --git a/modules/installation-osp-deploying-bare-metal-machines.adoc b/modules/installation-osp-deploying-bare-metal-machines.adoc index aca165da19..48c04ec6af 100644 --- a/modules/installation-osp-deploying-bare-metal-machines.adoc +++ b/modules/installation-osp-deploying-bare-metal-machines.adoc @@ -27,7 +27,7 @@ Be sure that your `install-config.yaml` file reflects whether the {rh-openstack} * The {rh-openstack} link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/bare_metal_provisioning/index[Bare Metal service (Ironic)] is enabled and accessible via the {rh-openstack} Compute API. -* Bare metal is available as link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/bare_metal_provisioning/sect-configure#creating_the_bare_metal_flavor[a {rh-openstack} flavor]. +* Bare metal is available as link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/bare_metal_provisioning/configuring-the-bare-metal-provisioning-service-after-deployment#creating-the-bare-metal-flavor_bare-metal-post-deployment[a {rh-openstack} flavor]. * The {rh-openstack} network supports both VM and bare metal server attachment. diff --git a/modules/migrating-reconcile-code.adoc b/modules/migrating-reconcile-code.adoc index c1270b149a..380dbf951f 100644 --- a/modules/migrating-reconcile-code.adoc +++ b/modules/migrating-reconcile-code.adoc @@ -71,7 +71,7 @@ Watching multiple resources lets you trigger the reconcile loop for multiple resources relevant to your application. See the link:https://godoc.org/github.com/kubernetes-sigs/controller-runtime/pkg#hdr-Watching_and_EventHandling[watching and eventhandling] documentation and the Kubernetes -link:https://github.com/kubernetes/community/blob/master/contributors/devel/controllers.md#guidelines[controller conventions] +link:https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/controllers.md[controller conventions] documentation for more details. + If your operator is watching more than one CR type, you can do one of the @@ -199,7 +199,7 @@ return reconcileResult, nil reconciler's client. + See the examples below and the `controller-runtime` -link:https://github.com/operator-framework/operator-sdk/blob/master/doc/user/client.md[client API documentation] +link:https://sdk.operatorframework.io/docs/building-operators/golang/references/client/[client API documentation] in the `operator-sdk` project for more details: + ---- @@ -268,7 +268,7 @@ However, if there are any Operator-specific flags or settings defined in the old `main.go` file, copy those over. + If you have any third party resource types registered with the SDK's scheme, see -link:https://github.com/operator-framework/operator-sdk/blob/master/doc/user-guide.md#adding-3rd-party-resources-to-your-operator[Advanced Topics] +link:https://sdk.operatorframework.io/docs/building-operators/golang/advanced-topics/#adding-3rd-party-resources-to-your-operator[Advanced Topics] in the `operator-sdk` project for how to register those with the Manager's scheme in the new project. diff --git a/modules/rhel-compute-available-hooks.adoc b/modules/rhel-compute-available-hooks.adoc index 167f31cdc8..4295851576 100644 --- a/modules/rhel-compute-available-hooks.adoc +++ b/modules/rhel-compute-available-hooks.adoc @@ -18,25 +18,25 @@ compute machines in your {product-title} cluster. a|- Runs *before* each node is cordoned. - This hook runs against *each node* in serial. - If a task must run against a different host, the task must use -link:http://docs.ansible.com/ansible/playbooks_delegation.html#delegation[`delegate_to` or `local_action`]. +link:https://docs.ansible.com/ansible/latest/user_guide/playbooks_delegation.html[`delegate_to` or `local_action`]. |`openshift_node_pre_upgrade_hook` a|- Runs *after* each node is cordoned but *before* it is updated. - This hook runs against *each node* in serial. - If a task must run against a different host, the task must use -link:http://docs.ansible.com/ansible/playbooks_delegation.html#delegation[`delegate_to` or `local_action`]. +link:https://docs.ansible.com/ansible/latest/user_guide/playbooks_delegation.html[`delegate_to` or `local_action`]. |`openshift_node_pre_uncordon_hook` a|- Runs *after* each node is updated but *before* it is uncordoned. - This hook runs against *each node* in serial. - If a task must run against a different host, they task must use -link:http://docs.ansible.com/ansible/playbooks_delegation.html#delegation[`delegate_to` or `local_action`]. +link:https://docs.ansible.com/ansible/latest/user_guide/playbooks_delegation.html[`delegate_to` or `local_action`]. |`openshift_node_post_upgrade_hook` a|- Runs *after* each node uncordoned. It is the *last* node update action. - This hook runs against *each node* in serial. - If a task must run against a different host, the task must use -link:http://docs.ansible.com/ansible/playbooks_delegation.html#delegation[`delegate_to` or `local_action`]. +link:https://docs.ansible.com/ansible/latest/user_guide/playbooks_delegation.html[`delegate_to` or `local_action`]. |=== diff --git a/modules/security-platform-authentication.adoc b/modules/security-platform-authentication.adoc index d5abae6e86..c8541d259e 100644 --- a/modules/security-platform-authentication.adoc +++ b/modules/security-platform-authentication.adoc @@ -35,7 +35,7 @@ access policy for groups of users. Application plans allow you to set rate limits for API usage and control traffic flow for groups of developers. For a tutorial on using APIcast v2, the containerized 3scale API Gateway, see -link:https://support.3scale.net/docs/deployment-options/apicast-openshift[Running APIcast on Red Hat OpenShift] +link:https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.0/html/deployment_options/apicast-openshift[Running APIcast on Red Hat OpenShift] in the 3scale documentation. [id="security-platform-red-hat-sso_{context}"] diff --git a/modules/virt-about-red-hat-ansible-automation.adoc b/modules/virt-about-red-hat-ansible-automation.adoc index 8620a460a4..1e991570ec 100644 --- a/modules/virt-about-red-hat-ansible-automation.adoc +++ b/modules/virt-about-red-hat-ansible-automation.adoc @@ -14,4 +14,4 @@ virtual machine operations. Ansible provides a way to automate {VirtProductName} management, which you can also accomplish by using the `oc` CLI tool or APIs. Ansible is unique because it allows you to integrate -link:https://docs.ansible.com/ansible/latest/modules/list_of_cloud_modules.html#kubevirt[KubeVirt modules] with other Ansible modules. +link:https://docs.ansible.com/ansible/2.9/modules/list_of_cloud_modules.html#ovirt[KubeVirt modules] with other Ansible modules. diff --git a/storage/persistent_storage/persistent-storage-iscsi.adoc b/storage/persistent_storage/persistent-storage-iscsi.adoc index 0b56b8800e..391f110ce1 100644 --- a/storage/persistent_storage/persistent-storage-iscsi.adoc +++ b/storage/persistent_storage/persistent-storage-iscsi.adoc @@ -7,7 +7,7 @@ toc::[] You can provision your {product-title} cluster with persistent storage using -https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/ch-iscsi.html[iSCSI]. +https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/managing_storage_devices/index#getting-started-with-iscsi_managing-storage-devices[iSCSI]. Some familiarity with Kubernetes and iSCSI is assumed. The Kubernetes persistent volume framework allows administrators to diff --git a/storage/persistent_storage/persistent-storage-ocs.adoc b/storage/persistent_storage/persistent-storage-ocs.adoc index e8ab563499..b1004bb0f9 100644 --- a/storage/persistent_storage/persistent-storage-ocs.adoc +++ b/storage/persistent_storage/persistent-storage-ocs.adoc @@ -37,7 +37,7 @@ OpenShift Container Storage on top of Red Hat Hyperconverged Infrastructure (RHH |link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_using_amazon_web_services/[Deploying OpenShift Container Storage 4.7 using Amazon Web Services] |Deploying Red Hat OpenShift Container Storage to local storage on bare metal infrastructure -|link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_using_bare_metal_infrastructure//[Deploying OpenShift Container Storage 4.7 using bare metal infrastructure] +|link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_using_bare_metal_infrastructure/[Deploying OpenShift Container Storage 4.7 using bare metal infrastructure] |Deploying Red Hat OpenShift Container Storage to use an external Red Hat Ceph Storage cluster |link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_in_external_mode/[Deploying OpenShift Container Storage 4.7 in external mode] @@ -58,7 +58,7 @@ OpenShift Container Storage on top of Red Hat Hyperconverged Infrastructure (RHH |link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_and_managing_openshift_container_storage_using_red_hat_openstack_platform/[Deploying and managing OpenShift Container Storage 4.7 using Red Hat OpenStack Platform] |Deploying and managing Red Hat OpenShift Container Storage on {rh-virtualization-first} -|link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_and_managing_openshift_container_storage_using_red_hat_virtualization_platform/[Deploying and managing OpenShift Container Storage 4.7 using Red Hat Virtualization Platform] +|link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_using_red_hat_virtualization_platform/index[Deploying and managing OpenShift Container Storage 4.7 using Red Hat Virtualization Platform] |Deploying Red Hat OpenShift Container Storage on VMware vSphere clusters |link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.7/html/deploying_openshift_container_storage_on_vmware_vsphere/[Deploying OpenShift Container Storage 4.7 on VMware vSphere] diff --git a/windows_containers/understanding-windows-container-workloads.adoc b/windows_containers/understanding-windows-container-workloads.adoc index e367f0379f..187d79e349 100644 --- a/windows_containers/understanding-windows-container-workloads.adoc +++ b/windows_containers/understanding-windows-container-workloads.adoc @@ -17,7 +17,7 @@ The following Windows Server operating systems are supported for {product-title} * Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019 -For more information, see Microsoft's documentation on link:https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19[Windows Server channels]. +For more information, see Microsoft's documentation on link:https://docs.microsoft.com/en-us/windows-server/get-started/editions-comparison-windows-server-2019[Windows Server channels]. [NOTE] ====