From 29cd1eac4ea5110a3dc12234e89aa8412768a161 Mon Sep 17 00:00:00 2001 From: Fred Rolland Date: Mon, 4 Aug 2025 16:32:39 +0300 Subject: [PATCH] fix: update broken links Signed-off-by: Fred Rolland --- docs/advanced/doca-drivers.rst | 2 +- docs/advanced/proxy-airgapped.rst | 2 +- docs/deployment-guide-kubernetes.rst | 2 +- docs/getting-started-openshift.rst | 14 +++++++------- docs/life-cycle-management.rst | 2 +- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/advanced/doca-drivers.rst b/docs/advanced/doca-drivers.rst index 505e3a88..57148868 100644 --- a/docs/advanced/doca-drivers.rst +++ b/docs/advanced/doca-drivers.rst @@ -164,7 +164,7 @@ RHCOS Prerequisites ~~~~~~~~~~~~~ -- Install `oc `_ CLI tool. +- Install `oc `_ CLI tool. - Download OpenShift `pull secret `_. ~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/advanced/proxy-airgapped.rst b/docs/advanced/proxy-airgapped.rst index 90f82303..041356fd 100644 --- a/docs/advanced/proxy-airgapped.rst +++ b/docs/advanced/proxy-airgapped.rst @@ -38,7 +38,7 @@ HTTP Proxy Configuration for Openshift -------------------------------------- For Openshift, it is recommended to use the cluster-wide Proxy object to provide proxy information for the cluster. -Please follow the procedure described in `Configuring the Cluster-wide Proxy `_ via the Red Hat Openshift public documentation. The NVIDIA Network Operator will automatically inject proxy related ENV into the driver container, based on the information present in the cluster-wide Proxy object. +Please follow the procedure described in `Configuring the Cluster-wide Proxy `_ via the Red Hat Openshift public documentation. The NVIDIA Network Operator will automatically inject proxy related ENV into the driver container, based on the information present in the cluster-wide Proxy object. ------------------------ HTTP Proxy Configuration diff --git a/docs/deployment-guide-kubernetes.rst b/docs/deployment-guide-kubernetes.rst index 533223b9..9a3541fe 100644 --- a/docs/deployment-guide-kubernetes.rst +++ b/docs/deployment-guide-kubernetes.rst @@ -1505,7 +1505,7 @@ Network Operator Deployment with an SR-IOV InfiniBand Network with PKey Manageme ---------------------------------------------------------------------------------- .. _this article: https://docs.mellanox.com/display/MLNXOFEDv51258060/OpenSM -.. _the project documentation: https://docs.nvidia.com/networking/display/UFMEnterpriseUMv652 +.. _the project documentation: https://docs.nvidia.com/networking/software/management-software/index.html#ufm-enterprise Network Operator deployment with InfiniBand network requires the following: diff --git a/docs/getting-started-openshift.rst b/docs/getting-started-openshift.rst index c059c1a4..7465a3e9 100644 --- a/docs/getting-started-openshift.rst +++ b/docs/getting-started-openshift.rst @@ -42,7 +42,7 @@ Network Operator Deployment on an OpenShift Container Platform Node Feature Discovery ---------------------- -To enable Node Feature Discovery, please follow the official `guide `_. +To enable Node Feature Discovery, please follow the official `guide `_. A single instance of Node Feature Discovery is expected to be used in the cluster. @@ -73,7 +73,7 @@ An example of Node Feature Discovery configuration: Verify that the following label is present on the nodes containing NVIDIA networking hardware: `feature.node.kubernetes.io/pci-15b3.present=true` -For more details please read official NFD `documentation `_. +For more details please read official NFD `documentation `_. .. code-block:: bash @@ -102,7 +102,7 @@ For more details please read official NFD `documentation `_ to install SR-IOV Network Operator on an OpenShift Container Platform. +If you are planning to use SR-IOV, follow these `instructions `_ to install SR-IOV Network Operator on an OpenShift Container Platform. .. warning:: The SR-IOV resources created will have the `openshift.io` prefix. @@ -116,7 +116,7 @@ For the default SriovOperatorConfig CR to work with the NVIDIA DOCA-OFED Driver --patch '{ "spec": { "configDaemonNodeSelector": { "network.nvidia.com/operator.mofed.wait": "false", "node-role.kubernetes.io/worker": "", "feature.node.kubernetes.io/pci-15b3.sriov.capable": "true" } } }' .. warning:: - SR-IOV Network Operator configuration documentation can be found on the `Official Website `_. + SR-IOV Network Operator configuration documentation can be found on the `Official Website `_. ------------ GPU Operator @@ -136,7 +136,7 @@ Network Operator Installation Using OpenShift Catalog - In the OpenShift Container Platform web console side menu, select Operators > OperatorHub, and search for the NVIDIA Network Operator. - Select NVIDIA Network Operator, and click Install in the first screen and in the subsequent one. -- For additional information, see the `Red Hat OpenShift Container Platform Documentation `_. +- For additional information, see the `Red Hat OpenShift Container Platform Documentation `_. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Network Operator Installation using OpenShift OC CLI @@ -529,6 +529,6 @@ The `pod.yaml` configuration file for such a deployment: Network Operator Deployment for DPDK Workloads - OCP """""""""""""""""""""""""""""""""""""""""""""""""""" -In order to configure `HUGEPAGES` in OpenShift, refer to this `steps `_. +In order to configure `HUGEPAGES` in OpenShift, refer to this `steps `_. -For SR-IOV Network Operator configuration instructions, visit the Official `Website `_. \ No newline at end of file +For SR-IOV Network Operator configuration instructions, visit the Official `Website `_. \ No newline at end of file diff --git a/docs/life-cycle-management.rst b/docs/life-cycle-management.rst index ac57fa99..ceaf9d8d 100644 --- a/docs/life-cycle-management.rst +++ b/docs/life-cycle-management.rst @@ -496,7 +496,7 @@ Make sure that the CRDs created during the operator installation have been remov Uninstalling the Network Operator on an OpenShift Cluster --------------------------------------------------------- -.. _Red Hat OpenShift Container Platform Documentation: https://docs.openshift.com/container-platform/4.10/operators/admin/olm-deleting-operators-from-cluster.html +.. _Red Hat OpenShift Container Platform Documentation: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/operators/administrator-tasks#olm-deleting-operators-from-a-cluster From the console: