Fixed dead links (#604)

* Fixed dead links

* Replaced hardcoded Turtles version with variable

(cherry picked from commit 06fa67c)

Author: fsundermeyer

asciidoc/components/turtles.adoc

@@ -12,7 +12,7 @@ ifdef::env-github[]
 endif::[]
 
 
-See Rancher Turtles documentation at https://turtles.docs.rancher.com/turtles/{rancher-turtles-docs-version}
+See Rancher Turtles documentation at https://documentation.suse.com/cloudnative/cluster-api/
 
 [quote]
 ____

asciidoc/edge-book/links.adoc

@@ -83,6 +83,7 @@
 :link-atip-examples: https://github.com/suse-edge/atip/tree/{release-tag-atip}/telco-examples/edge-clusters
 :link-atip-performance-settings: https://github.com/suse-edge/atip/blob/{release-tag-atip}/telco-examples/edge-clusters/dhcp/eib/custom/files/performance-settings.sh
 :link-atip-sriov-auto-filler: https://github.com/suse-edge/atip/blob/{release-tag-atip}/telco-examples/edge-clusters/dhcp/eib/custom/files/sriov-auto-filler.sh
-:link-atip-sriov-operator-values: https://github.com/suse-edge/charts/blob/{release-tag-atip}/charts/sriov-network-operator/{version-sriov-network-operator-chart}/values.yaml
+:link-atip-sriov-operator-values: https://github.com/suse-edge/charts/blob/main/charts/sriov-network-operator/1.4.0/values.yaml
+//:link-atip-sriov-operator-values: https://github.com/suse-edge/charts/blob/{release-tag-atip}/charts/sriov-network-operator/{version-sriov-network-operator-chart}/values.yaml
 
 :link-atip-micro-download-url: https://download.opensuse.org/repositories/isv:/SUSE:/Edge:/Telco/SL-Micro_6.0_images/

asciidoc/guides/metallb-kube-api.adoc

@@ -134,7 +134,7 @@ systemctl restart ${KUBE_DISTRIBUTION}
 
 == Installing MetalLB
 
-To deploy `MetalLB`, the https://suse-edge.github.io/docs/quickstart/metallb[MetalLB on K3s] guide can be used.
+To deploy `MetalLB`, the <<guides-metallb-k3s,MetalLB on K3s>> guide can be used.
 
 *NOTE:* Ensure that the IP addresses of the `ip-pool` IPAddressPool do not overlap with the IP addresses previously selected for the `LoadBalancer` service.
 

asciidoc/integrations/nats.adoc

@@ -122,12 +122,12 @@ There is an already merged PR which makes the built-in NATS in K3s straightforwa
 
 For this reason, the K3s binary should be built manually.
 
-In this tutorial, https://suse-edge.github.io/docs/quickstart/slemicro-utm-aarch64[SUSE Linux Micro on OSX on Apple Silicon (UTM)] VM is used.
+//In this tutorial, https://suse-edge.github.io/docs/quickstart/slemicro-utm-aarch64[SUSE Linux Micro on OSX on Apple Silicon (UTM)] VM is used.
 
-[NOTE]
-====
-Run the commands below on the OSX PC.
-====
+//[NOTE]
+//====
+//Run the commands below on the OSX PC.
+//====
 
 ==== Building K3s
 

asciidoc/integrations/nvidia-slemicro.adoc

@@ -16,7 +16,9 @@ This guide demonstrates how to implement host-level NVIDIA GPU support via the p
 
 It is important to call out that the support for these drivers is provided by both SUSE and NVIDIA in tight collaboration, where the driver is built and shipped by SUSE as part of the package repositories. However, if you have any concerns or questions about the combination in which you use the drivers, ask your SUSE or NVIDIA account managers for further assistance. If you plan to use https://www.nvidia.com/en-gb/data-center/products/ai-enterprise/[NVIDIA AI Enterprise] (NVAIE), ensure that you are using an https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/platform-support.html#supported-nvidia-gpus-and-systems[NVAIE certified GPU], which _may_ require the use of proprietary NVIDIA drivers. If you are unsure, speak with your NVIDIA representative.
 
-Further information about NVIDIA GPU operator integration is _not_ covered in this guide. While integrating the NVIDIA GPU Operator for Kubernetes is not covered here, you can still follow most of the steps in this guide to set up the underlying operating system and simply enable the GPU operator to use the _pre-installed_ drivers via the `driver.enabled=false` flag in the NVIDIA GPU Operator Helm chart, where it will simply pick up the installed drivers on the host. More comprehensive instructions are available from NVIDIA https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/install-gpu-operator.html#chart-customization-options[here]. SUSE recently also made a https://documentation.suse.com/trd/kubernetes/single-html/gs_rke2-slebci_nvidia-gpu-operator/[Technical Reference Document] (TRD) available that discusses how to use the GPU operator and the NVIDIA proprietary drivers, should this be a requirement for your use case.
+Further information about NVIDIA GPU operator integration is _not_ covered in this guide. While integrating the NVIDIA GPU Operator for Kubernetes is not covered here, you can still follow most of the steps in this guide to set up the underlying operating system and simply enable the GPU operator to use the _pre-installed_ drivers via the `driver.enabled=false` flag in the NVIDIA GPU Operator Helm chart, where it will simply pick up the installed drivers on the host. More comprehensive instructions are available from NVIDIA https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/install-gpu-operator.html#chart-customization-options[here].
+//This doc seems to have vanished from d.s.c.
+//SUSE recently also made a https://documentation.suse.com/trd/kubernetes/single-html/gs_rke2-slebci_nvidia-gpu-operator/[Technical Reference Document] (TRD) available that discusses how to use the GPU operator and the NVIDIA proprietary drivers, should this be a requirement for your use case.
 
 == Prerequisites
 

asciidoc/misc/rke2-selinux.adoc

@@ -14,8 +14,7 @@ endif::[]
 
 == Prerequisites
 
-* one VM. Hint https://suse-edge.github.io/docs/quickstart/slemicro-utm-aarch64[SUSE Linux Micro on OSX on Apple Silicon (UTM)] or https://suse-edge.github.io/docs/quickstart/slemicro-virt-install-x86_64[SUSE Linux Micro on X86_64 on libvirt (virt-install)] can be used as the base platform for validation here, but these instructions should work on any SUSE Linux Micro based system.
- ** The VM should meet the https://docs.rke2.io/install/requirements#linuxwindows[RKE2 requirements].
+One VM meeting the https://docs.rke2.io/install/requirements#linuxwindows[RKE2 requirements].
 
 == Installation
 

asciidoc/product/atip-features.adoc

@@ -1249,7 +1249,7 @@ For the registry changes to take effect, you need to either configure this file
 
 [NOTE]
 ====
-For more information about this, please check https://docs.rke2.io/install/containerd_registry_configuration#registries-configuration-file[containerd registry configuration rke2].
+For more information about this, please check https://documentation.suse.com/cloudnative/rke2/latest/en/install/containerd_registry_configuration.html#_registries_configuration_file[containerd registry configuration rke2].
 ====
 
 [#ptp-configuration]

asciidoc/product/atip-management-cluster.adoc

@@ -984,7 +984,7 @@ The following is an example of the `mgmt-cluster.yaml` file with the `embeddedAr
 Make sure to the listed images contain the component versions you need.
 ====
 
-The `rancher-turtles-airgap-resources` helm chart must also be added, this creates resources as described in the https://turtles.docs.rancher.com/getting-started/air-gapped-environment[Rancher Turtles Airgap Documentation].  This also requires a turtles.yaml values file for the rancher-turtles chart to specify the necessary configuration.
+The `rancher-turtles-airgap-resources` helm chart must also be added, this creates resources as described in the https://documentation.suse.com/cloudnative/cluster-api/{rancher-turtles-docs-version}/en/getting-started/air-gapped-environment.html[Rancher Turtles Airgap Documentation].  This also requires a turtles.yaml values file for the rancher-turtles chart to specify the necessary configuration.
 
 [,yaml,subs="attributes"]
 ----