[DOCS] Fix broken links (#373)

wiwaszko-intel · sgolebiewski-intel · web-flow · commit 1f52edbaf9e8 · 2026-02-10T11:35:14.000+01:00
* [DOCS] EMF fix docu links temp

* Fixing broken links

* [DOCS] Fixing broken links

* [DOCS] fix missing TODO link

---------

Co-authored-by: Golebiewski, SebastianX &lt;sebastianx.golebiewski@intel.com&gt;
diff --git a/docs/deployment_guide/cloud_deployment/cloud_advanced/cloud_manual_modules.rst b/docs/deployment_guide/cloud_deployment/cloud_advanced/cloud_manual_modules.rst
@@ -21,7 +21,7 @@ Add configuration for modules
 +++++++++++++++++++++++++++++
 
 Each ``backend.tf`` file contains three values: ``region``, ``bucket``, and ``key``. These values are the same
-used during `Terraform configuration <adv_manual_terraconfig>`_.
+used during `Terraform configuration <./cloud_manual_terraconfig.html>`_.
 
 Every environment must use a unique region, bucket, and key combination. Terraform can't distinguish between environments.
 
diff --git a/docs/deployment_guide/cloud_deployment/cloud_get_started/index.rst b/docs/deployment_guide/cloud_deployment/cloud_get_started/index.rst
@@ -53,13 +53,13 @@ Supported AWS regions
 Edge Orchestrator must be installed to an AWS Region with at least **three**
 `Availability Zones* <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-availability-zones>`_.
 
-You can use an `AWS Region map <https://www.cloudregions.io/aws/regions-map>`_ that lists Availability Zones per region to verify
+You can use an `AWS Region map <https://aws.amazon.com/about-aws/global-infrastructure/regions_az/>`_ that lists Availability Zones per region to verify
 that the AWS Region you plan to install to has a minimum of three Availability Zones.
 
 The Edge Orchestrator installer will verify that the selected AWS Region has at least three Availability Zones and error out if the requirement is not met.
 
 For Firewall configuration, see
-`Firewall Configuration </../../shared/shared_gs_iam>`__
+`Firewall Configuration <../../../shared/shared_gs_firewall_config.html>`__
 
 .. toctree::
    :hidden:
diff --git a/docs/deployment_guide/cloud_deployment/cloud_how_to/cloud_scale_orch.rst b/docs/deployment_guide/cloud_deployment/cloud_how_to/cloud_scale_orch.rst
@@ -169,7 +169,7 @@ Update Cluster Scale Settings
 .. note::
    Scaling Edge Orchestrator cluster may require changing of observability profile.
    For details on observability profiles, see
-   `Observability Configuration <../../cloud_deployment/cloud_get_started/system_requirements_aws_orch#edge-orchestrator-observability-configuration>`__.
+   `Observability Configuration <../../cloud_deployment/cloud_get_started/system_requirements_aws_orch.html#edge-orchestrator-observability-configuration>`__.
 
 .. note::
    When updating the cluster scale, you also need to provide flags from the installation step;
diff --git a/docs/deployment_guide/cloud_deployment/cloud_how_to/cloud_uninstall.rst b/docs/deployment_guide/cloud_deployment/cloud_how_to/cloud_uninstall.rst
@@ -45,4 +45,4 @@ Uninstall Edge Orchestrator with no load balancer installed
 
 
 For a full list of flags available, see
-`flag examples <../cloud_examples/cloud_flags#flag-examples>`__.
+`flag examples <../cloud_examples/cloud_flags.html>`__.
diff --git a/docs/deployment_guide/on_prem_deployment/on_prem_get_started/index.rst b/docs/deployment_guide/on_prem_deployment/on_prem_get_started/index.rst
@@ -297,7 +297,7 @@ To install Edge Orchestrator and Edge Node, the following Egress rules are requi
     -  https://github.com/
     -  Container images
   * -  Edge Orchestrator
-    -  https://kubernetes.github.io/
+    -  https://kubernetes.io/
     -  Helm Chart
   * -  Edge Orchestrator
     -  https://charts.external-secrets.io/
@@ -315,22 +315,22 @@ To install Edge Orchestrator and Edge Node, the following Egress rules are requi
     -  https://kiali.org/
     -  Helm Chart
   * -  Edge Orchestrator
-    -  https://kyverno.github.io/
+    -  https://kyverno.github.io/kyverno/
     -  Helm Chart
   * -  Edge Orchestrator
-    -  https://metallb.github.io/
+    -  https://metallb.io/
     -  Helm Chart
   * -  Edge Orchestrator
-    -  https://prometheus-community.github.io/
+    -  https://github.com/prometheus-community/helm-charts
     -  Helm Chart
   * -  Edge Orchestrator
     -  https://charts.bitnami.com/
     -  Helm Chart
   * -  Edge Orchestrator
-    -  https://stakater.github.io/
+    -  https://github.com/stakater/
     -  Helm Chart
   * -  Edge Orchestrator
-    -  https://helm.traefik.io/
+    -  https://github.com/traefik/traefik-helm-chart
     -  Helm Chart
   * -  Edge Orchestrator
     -  https://helm.releases.hashicorp.com
@@ -387,7 +387,7 @@ To install Edge Orchestrator and Edge Node, the following Egress rules are requi
     -  https://\*.archive.ubuntu.com
     -  Onboarding
   * -  Edge Node
-    -  https://ppa.launchpad.net
+    -  https://launchpad.net/+tour/ppa
     -  Onboarding
   * -  Edge Node
     -  https://esm.ubuntu.com
diff --git a/docs/deployment_guide/on_prem_deployment/on_prem_how_to/on_prem_certificates.rst b/docs/deployment_guide/on_prem_deployment/on_prem_how_to/on_prem_certificates.rst
@@ -51,7 +51,7 @@ Create an Amazon Certificate
 If you use the AWS DNS service, see `Requesting a public certificate <https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html>`_.
 
 Verify that your Amazon certificate matches the
-`Certificate Requirements <../../cloud_deployment/cloud_how_to/cloud_certificates#new-certificate-requirements>`__
+`Certificate Requirements <../../cloud_deployment/cloud_how_to/cloud_certificates.html#new-certificate-requirements>`__
 before completing it.
 
 Generate a New Certificate with CSR Generator
diff --git a/docs/developer_guide/agents/arch/platform_observability.rst b/docs/developer_guide/agents/arch/platform_observability.rst
@@ -427,14 +427,14 @@ Platform Observability Agent depends on |software_prod_name| endpoints:
 Platform Observability Agent external telemetry collectors:
 
 - Official `fluent-bit
-  <https://docs.fluentbit.io/manual/installation/linux/ubuntu>`_ Debian
+  <https://docs.fluentbit.io/manual/installation/downloads/linux/ubuntu>`_ Debian
   package.
 
 - Official `telegraf <https://docs.influxdata.com/telegraf/v1/install/>`_
   Debian package.
 
 - Official `Otel Collector
-  <https://opentelemetry.io/docs/collector/installation/#deb-installation>`_
+  <https://opentelemetry.io/docs/collector/install/binary/linux/#deb-installation>`_
   Debian package.
 
 .. figure:: ./images/poa-system.png
diff --git a/docs/developer_guide/agents/arch/reporting.rst b/docs/developer_guide/agents/arch/reporting.rst
@@ -193,11 +193,11 @@ which must be provided in the ``/etc/edge-node/metrics/token`` file in the forma
 
 TLS version 1.3 is used for backend communication if supported by the server; otherwise, TLS 1.2 is used.
 
-The user running the application should be added to the `sudoers file <https://github.com/open-edge-platform/edge-node-agents/blob/main/config/sudoers.d/reporting-agent>`_,
+The user running the application should be added to the `sudoers file <https://github.com/open-edge-platform/edge-node-agents/blob/main/reporting-agent/config/sudoers.d/reporting-agent>`_,
 as the ``dmidecode`` and ``lshw`` applications require such privileges.
 
 The same user must also have execute access to the ``kubectl`` binary and read access to the ``kubeconfig`` file.
-The paths to these files are specified in the ``reporting-agent.yaml`` `configuration file <https://github.com/open-edge-platform/edge-node-agents/blob/main/config/reporting-agent.yaml>`_.
+The paths to these files are specified in the ``reporting-agent.yaml`` `configuration file <https://github.com/open-edge-platform/edge-node-agents/blob/main/reporting-agent/config/reporting-agent.yaml>`_.
 
 Auditing
 ~~~~~~~~
diff --git a/docs/developer_guide/application_developer_workflow/deployment-helm/index.rst b/docs/developer_guide/application_developer_workflow/deployment-helm/index.rst
@@ -151,7 +151,7 @@ properly:
       helm -n testns template --release-name foobar . -f <values.yaml from deployment package>
 
 #. Be aware of the preinstalled network policies applied to various namespaces on the Edge Node cluster.
-   These can be seen in `network-policies  <https://github.com/open-edge-platform/cluster-extensions/tree/main/helm/network-policies/templates>`_
+   These can be seen in `network-policies  <https://github.com/open-edge-platform/cluster-extensions/tree/main/helm/>`_
    or by running `kubectl` on the Edge Node:
 
    .. code:: shell
@@ -194,7 +194,7 @@ properly:
    dependent on any specific configuration, then default configuration can be left as is.
 
 #. Scan the Helm Chart for security vulnerabilities. This can be done using
-   `Trivy <https://trivy.dev/latest/>`_.
+   `Trivy <https://trivy.dev/docs/latest/guide/>`_.
 
    .. code:: shell
 
diff --git a/docs/developer_guide/application_developer_workflow/packaging-applications/index.rst b/docs/developer_guide/application_developer_workflow/packaging-applications/index.rst
@@ -111,7 +111,7 @@ integrity of containerized applications. Some key practices include:
 
 There are many online guides with more details on these practices.
 
-The `Trivy\* <https://trivy.dev/latest/>`_ tool can be used to scan images for
+The `Trivy\* <https://trivy.dev/docs/latest/getting-started/>`_ tool can be used to scan images for
 vulnerabilities. It can be installed locally or added to a CI check. The following
 command will scan the image:
 
diff --git a/docs/developer_guide/infra_manager/arch/hl_architecture.rst b/docs/developer_guide/infra_manager/arch/hl_architecture.rst
@@ -19,7 +19,7 @@ manage, monitor, control and perform overall lifecycle management of physical
 equipment inventory deployed at the edge locations. It is made up of the
 following key components and services:
 
-`API <https://github.com/open-edge-platform/infra-core/tree/main/api>`_ provides a northbound REST API that can be accessed by users and other
+`API <https://github.com/open-edge-platform/infra-core/tree/main/apiv2>`_ provides a northbound REST API that can be accessed by users and other
 Open Edge Platform services. It is a horizontally scalable stateless
 service.
 
diff --git a/docs/developer_guide/infra_manager/tutorials/new_resource/api.rst b/docs/developer_guide/infra_manager/tutorials/new_resource/api.rst
@@ -1,7 +1,7 @@
 REST APIs
 =========
 
-This section covers the process of generating `REST APIs <https://github.com/open-edge-platform/infra-core/tree/main/api>`_ for a new resource.
+This section covers the process of generating `REST APIs <https://github.com/open-edge-platform/infra-core/tree/main/apiv2>`_ for a new resource.
 Let's continue with the example of the ``localaccount`` resource.
 
 OAPI Definitions
diff --git a/docs/developer_guide/infra_manager/tutorials/upgrade/orch_upgrade.rst b/docs/developer_guide/infra_manager/tutorials/upgrade/orch_upgrade.rst
@@ -24,7 +24,7 @@ Full Upgrade of the Edge Orchestrator Platform in Production Environment
 
 Starting with version 3.1, operators running an earlier version of Edge Orchestrator are expected
 to be able to perform a seamless upgrade of the entire platform to the latest release.
-The  `Orchestrator upgrade guide <TODO link>`_  provides the instructions for the operator to perform this upgrade.
+The  `Orchestrator upgrade guide <https://docs.openedgeplatform.intel.com/edge-manage-docs/dev/deployment_guide/cloud_deployment/cloud_how_to/cloud_upgrade.html>`_  provides the instructions for the operator to perform this upgrade.
 
 .. note::
 
@@ -47,10 +47,10 @@ To do so, users can modify the chart revision of the following applications:
 - infra-external
 - infra-onboarding
 
-Using the platform’s web UI, developers can then verify the upgraded Orchestrator by:
+Using the platform's web UI, developers can then verify the upgraded Orchestrator by:
 
 - Onboarding an Edge Node (EN)
-- Monitoring the EN’s status
+- Monitoring the EN status
 - Performing an EN upgrade
 
 The following section provides step-by-step instructions for developers to upgrade the Edge Manageability applications and to verify
diff --git a/docs/release_notes/2025.2/containers_helm_charts_2025.2.rst b/docs/release_notes/2025.2/containers_helm_charts_2025.2.rst
@@ -676,7 +676,7 @@ Helm Charts for Platform services components
      - istio-system
      - "100"
      - istio-base
-     - https://istio-release.storage.googleapis.com/charts
+     - https://istio.io/latest/docs/setup/install/helm/
      - 1.28.0
    * - 2
      - istio-policy
@@ -692,7 +692,7 @@ Helm Charts for Platform services components
      - istio-system
      - "110"
      - istiod
-     - https://istio-release.storage.googleapis.com/charts
+     - https://istio-release.storage.googleapis.com
      - 1.28.0
    * - 4
      - kiali
diff --git a/docs/release_notes/2025.2/third_party_components_2025.2.rst b/docs/release_notes/2025.2/third_party_components_2025.2.rst
@@ -25,11 +25,11 @@ Application Orchestration
      - v0.12.8
    * - Fleet-Controller
      - Helm
-     - https://rancher.github.io/fleet-helm-charts/flleet:0.12.8
+     - https://github.com/rancher/fleet/releases/tag/v0.12.8
      - 0.12.8
    * - Fleet-CRD
      - Helm
-     - https://rancher.github.io/fleet-helm-charts/fleet-crd:0.12.8
+     - https://github.com/rancher/fleet/releases/download/v0.12.8/fleet-crd-0.12.8.tgz
      - 0.12.8
    * - Fleet-Agent
      - Container
@@ -73,7 +73,7 @@ Application Orchestration
      - v2.13.2
    * - Harbor
      - Helm
-     - https://helm.goharbor.io/harbor:1.17.2
+     - https://github.com/goharbor/harbor-helm/releases/tag/v1.17.2
      - 1.17.2
 
 Cluster Orchestration
diff --git a/docs/release_notes/3.0/containers_helm_charts_3.0.rst b/docs/release_notes/3.0/containers_helm_charts_3.0.rst
@@ -938,7 +938,7 @@ Helm Charts for Platform services components
      - orch-database
      - "140"
      - postgresql
-     - https://charts.bitnami.com/bitnami
+     - https://charts.bitnami.com
      - 15.5.26
    * - 2
      - postgresql-secrets
diff --git a/docs/release_notes/3.0/third_party_components_3.0.rst b/docs/release_notes/3.0/third_party_components_3.0.rst
@@ -24,11 +24,11 @@ Application Orchestration
      -
    * - Fleet-Controller
      - Helm*
-     - https://rancher.github.io/fleet-helm-charts/fleet
+     - https://rancher.github.io/fleet-helm-charts/
      - 0.10.2
    * - Fleet-CRD
      - Helm
-     - https://rancher.github.io/fleet-helm-charts/fleet-crd
+     - https://fleet.rancher.io/
      - 0.10.2
    * - Fleet-Agent
      - Container
@@ -72,7 +72,7 @@ Application Orchestration
      - v2.12.2
    * - Harbor
      - Helm
-     - https://helm.goharbor.io/harbor
+     - https://goharbor.io/docs/1.10/install-config/harbor-ha-helm/
      - 1.16.2
 
 Cluster Orchestration
@@ -271,7 +271,7 @@ Edge Infrastructure Manager
      - sha256:fe8a5ee49f613495df3b57afa86b39f081bd1b3b9ed61248f46c3d3d7df56092
    * - busybox
      - Container (utility)
-     - https://hub.docker.com//busybox/
+     - https://hub.docker.com/_/busybox/
      - 1.36.1
 
 Platform services
diff --git a/docs/release_notes/3.1/third_party_components_3.1.rst b/docs/release_notes/3.1/third_party_components_3.1.rst
@@ -25,11 +25,11 @@ Application Orchestration
      - 0.12.1
    * - Fleet-Controller
      - Helm*
-     - https://rancher.github.io/fleet-helm-charts/fleet
+     - https://rancher.github.io/fleet-helm-charts/
      - 0.12.2
    * - Fleet-CRD
      - Helm
-     - https://rancher.github.io/fleet-helm-charts/fleet-crd
+     - https://rancher.github.io/fleet-helm-charts/
      - 0.12.2
    * - Fleet-Agent
      - Container
@@ -73,7 +73,7 @@ Application Orchestration
      - v2.13.0
    * - Harbor
      - Helm
-     - https://helm.goharbor.io/harbor
+     - https://goharbor.io/docs/1.10/install-config/harbor-ha-helm/
      - 1.17.0
 
 Cluster Orchestration
@@ -215,11 +215,11 @@ Cluster Extensions
      - 7.13.0
    * - nvidia-gpu-operator
      - Helm/Container
-     - https://helm.ngc.nvidia.com/nvidia/gpu-operator
+     - https://catalog.ngc.nvidia.com/orgs/nvidia/containers/gpu-operator?version=v25.3.0
      - v25.3.0
    * - intel-device-plugins-operator
      - Helm/Container
-     - https://intel.github.io/helm-charts/intel-device-plugins-gpu
+     - https://github.com/intel/helm-charts/tree/main/charts/gpu-device-plugin
      - 0.29.0
 
 Edge Infrastructure Manager
@@ -256,7 +256,7 @@ Edge Infrastructure Manager
      - sha256:fe8a5ee49f613495df3b57afa86b39f081bd1b3b9ed61248f46c3d3d7df56092
    * - busybox
      - Container (utility)
-     - https://hub.docker.com//busybox/
+     - https://hub.docker.com/_/busybox/
      - 1.36.1
    * - mps
      - Container
@@ -769,7 +769,7 @@ Trusted Compute
      -
    * - kata
      - Containers, scripts, ...
-     - https://github.com/kata-containers/kata-containers/releases/download/3.13.1/kata-static-3.13.1-amd64.tar.xz
+     - https://github.com/kata-containers/kata-containers/releases/tag/3.13.0
      -
    * - Debian Bookworm
      - Containers and binaries
diff --git a/docs/shared/shared_ao_co_o11y.rst b/docs/shared/shared_ao_co_o11y.rst
@@ -184,7 +184,7 @@ each edge node by connecting via SSH.
    To access edge nodes when observability is disabled, the edge node must be onboarded
    with **SSH enabled** in the configuration.
 
-   For details on how to add SSH users, refer to the `Local SSH Account Management <../user_guide/set_up_edge_infra/orch_cli/orch_cli_guide.rst#local-ssh-account-management>`_ section in the orch-cli guide.
+   For details on how to add SSH users, refer to the `Local SSH Account Management <../user_guide/set_up_edge_infra/orch_cli/orch_cli_guide.html#local-ssh-account-management>`_ section in the orch-cli guide.
 
 ----------------------------------------------------
 4.6.1 SSH Login to Edge Node
diff --git a/docs/shared/shared_gs_firewall_config.rst b/docs/shared/shared_gs_firewall_config.rst
diff --git a/docs/shared/shared_ht_iam_groups.rst b/docs/shared/shared_ht_iam_groups.rst
diff --git a/docs/shared/shared_ts_rs_token.rst b/docs/shared/shared_ts_rs_token.rst
diff --git a/docs/user_guide/package_software/extensions/trusted_compute_package.rst b/docs/user_guide/package_software/extensions/trusted_compute_package.rst
diff --git a/docs/user_guide/package_software/push_registry.rst b/docs/user_guide/package_software/push_registry.rst
diff --git a/docs/user_guide/package_software/quick_start_guide.rst b/docs/user_guide/package_software/quick_start_guide.rst

Original file line number	Diff line number	Diff line change
`@@ -45,4 +45,4 @@ Uninstall Edge Orchestrator with no load balancer installed`
`45`	`45`
`46`	`46`
`47`	`47`	`For a full list of flags available, see`
`48`		-`flag examples <../cloud_examples/cloud_flags#flag-examples>`__.
	`48`	+`flag examples <../cloud_examples/cloud_flags.html>`__.