AI: fixed underscore section IDs

Author: tbazant

ai-prompts/Import-Rancher-docs.md

@@ -22,4 +22,4 @@ Convert `xref:` calls that point to a relative path into external `link:` calls.
 
 *   Derive the new URL by appending the relative path to the base URL found in the file's top comment.
 *   Replace the `.adoc` file extension with `.html`.
-*   Match cross references that start with underline such as '_features_for_all_registered_clusters' with the right section by its name and prepend the section with corresponding ID such as [#_features_for_all_registered_clusters]
+*   Match cross references that start with underline such as 'features-for-all-registered-clusters' with the right section by its name and prepend the section with corresponding ID such as [#features-for-all-registered-clusters]

tasks/NVIDIA-Operator-installation.adoc

@@ -28,7 +28,7 @@ endif::[]
 :override-abstract!:
 :override-title!:
 
-[#_host_os_requirements]
+[#host-os-requirements]
 == Host OS requirements
 
 To expose the GPU to the pod correctly, the NVIDIA kernel drivers and the `libnvidia-ml` library must be correctly installed in the host OS. The NVIDIA Operator can automatically install drivers and libraries on some operating systems. Refer to the NVIDIA documentation for information on https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/platform-support.html#supported-operating-systems-and-kubernetes-platforms[supported operating system releases]. The installation of the NVIDIA components on your host OS is out of the scope of this documentation, refer to the NVIDIA documentation for instructions.
@@ -119,7 +119,7 @@ After one minute approximately, you can perform the following checks to verify t
 kubectl get node $NODENAME -o jsonpath='{.metadata.labels}' | grep "nvidia.com/gpu.deploy.driver"
 ----
 +
-You should see the value `pre-installed`. If you see `true`, the drivers were not correctly installed. If the <<_host_os_requirements,pre-requirements>> were correct, it is possible that you forgot to reboot the node after installing all packages.
+You should see the value `pre-installed`. If you see `true`, the drivers were not correctly installed. If the <<host-os-requirements,pre-requirements>> were correct, it is possible that you forgot to reboot the node after installing all packages.
 +
 You can also check other driver labels with:
 +

tasks/Rancher-installation-airgapped-kubernetes.adoc

@@ -37,7 +37,7 @@ The steps to set up an air-gapped Kubernetes cluster on RKE2 or K3s are shown be
 --
 In this guide, we are assuming you have created your nodes in your air-gapped environment and have a secure Docker private registry on your bastion server.
 
-[#_1_create_rke2_configuration]
+[#create-rke2-configuration]
 == 1. Create RKE2 configuration
 
 Create the `config.yaml` file at `/etc/rancher/rke2/config.yaml`. This will contain all the configuration options necessary to create a highly available RKE2 cluster.
@@ -67,7 +67,7 @@ For more information, refer to the https://documentation.suse.com/cloudnative/rk
 RKE2 additionally provides a `resolv-conf` option for kubelets, which may help with configuring DNS in air-gap networks.
 ====
 
-[[_2_create_registry_yaml]]
+[[create-registry-yaml]]
 == 2. Create Registry YAML
 
 Create the `registries.yaml` file at `/etc/rancher/rke2/registries.yaml`. This will tell RKE2 the necessary details to connect to your private registry.
@@ -94,7 +94,7 @@ configs:
 For more information on private registries configuration file for RKE2, refer to the https://documentation.suse.com/cloudnative/rke2/latest/en/install/containerd_registry_configuration.html[RKE2 documentation.]
 
 
-[[_3_install_rke2]]
+[[install-rke2]]
 == 3. Install RKE2
 
 Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the link:https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/[SUSE Rancher Support Matrix].
@@ -124,7 +124,7 @@ systemctl start rke2-server.service
 
 For more information, refer to the https://documentation.suse.com/cloudnative/rke2/latest/en/install/airgap.html[RKE2 documentation].
 
-[[_4_save_and_start_using_the_kubeconfig_file]]
+[[save-and-start-using-the-kubeconfig-file]]
 == 4. Save and Start Using the kubeconfig File
 
 When you installed RKE2 on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/rke2/rke2.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location.
@@ -165,7 +165,7 @@ kubectl --kubeconfig ~/.kube/config/rke2.yaml get pods --all-namespaces
 
 For more information about the `kubeconfig` file, refer to the https://documentation.suse.com/cloudnative/rke2/latest/en/cluster_access.html[RKE2 documentation] or the https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/[official Kubernetes documentation] about organizing cluster access using `kubeconfig` files.
 
-[#_note_on_upgrading]
+[#note-on-upgrading]
 == Note on Upgrading
 
 Upgrading an air-gap environment can be accomplished in the following manner:

tasks/Rancher-installation-airgapped-rancher.adoc

@@ -68,7 +68,7 @@ helm fetch rancher-prime/rancher --version=<version>
 ----
 
 === 2. Choose your SSL Configuration
-[[_2_choose_your_ssl_configuration]]
+[[choose-your-ssl-configuration]]
 
 The {ranchermanager} server is designed to be secure by default and requires SSL/TLS configuration.
 
@@ -119,7 +119,7 @@ When setting up the Rancher Helm template, there are several options in the Helm
 
 === 3. Fetch the Cert-Manager Chart
 
-Based on the choice your made in <<_2_choose_your_ssl_configuration,2. Choose your SSL Configuration>>, complete one of the procedures below.
+Based on the choice your made in <<choose-your-ssl-configuration,2. Choose your SSL Configuration>>, complete one of the procedures below.
 
 ==== Option A: Default Self-Signed Certificate
 

tasks/Rancher-installation-quickstart.adoc

@@ -118,17 +118,17 @@ There are three recommended options for the source of the certificate used for T
 
 | Rancher Generated Certificates (Default)
 | `ingress.tls.source=rancher`
-| <<_4_install_cert_manager,yes>>
+| <<install-cert-manager,yes>>
 
 | Let's Encrypt
 | `ingress.tls.source=letsEncrypt`
-| <<_4_install_cert_manager,yes>>
+| <<install-cert-manager,yes>>
 
 | Certificates from Files
 | `ingress.tls.source=secret`
 | no
 |===
-[#_4_install_cert_manager]
+[#install-cert-manager]
 === 4. Install cert-manager
 
 ____

tasks/Rancher-register-clusters.adoc

@@ -27,7 +27,7 @@ endif::[]
 
 The cluster registration feature replaced the feature to import clusters.
 
-The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see <<_management_capabilities_for_registered_clusters,Management Capabilities for Registered Clusters.>>
+The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see <<management-capabilities-for-registered-clusters,Management Capabilities for Registered Clusters.>>
 
 == Prerequisites
 
@@ -81,7 +81,7 @@ endif::[]
 . If you are importing a generic Kubernetes cluster in Rancher, perform the following steps for setup:
 .. Click **Agent Environment Variables** under **Cluster Options** to set environment variables for link:https://documentation.suse.com/cloudnative/rancher-manager/v2.13/en/cluster-deployment/about-rancher-agents.html[rancher cluster agent]. The environment variables can be set using key value pairs. If rancher agent requires use of proxy to communicate with Rancher server, `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables can be set using agent environment variables.
 .. Enable Project Network Isolation to ensure the cluster supports Kubernetes `NetworkPolicy` resources. Users can select the **Project Network Isolation** option under the **Advanced Options** dropdown to do so.
-.. <<_configuring_version_management_for_suse_rancher_prime_rke2_and_suse_rancher_prime_k3s_clusters,Configure the version management feature for imported RKE2 and K3s clusters>>.
+.. <<configuring-version-management-for-suse-rancher-prime-rke2-and-suse-rancher-prime-k3s-clusters,Configure the version management feature for imported RKE2 and K3s clusters>>.
 . Click *Create*.
 . The prerequisite for `cluster-admin` privileges is shown (see *Prerequisites* above), including an example command to fulfil the prerequisite.
 . Copy the `kubectl` command to your clipboard and run it on a node where kubeconfig is configured to point to the cluster you want to import. If you are unsure it is configured correctly, run `kubectl get nodes` to verify before running the command shown in Rancher.
@@ -149,21 +149,21 @@ resource "rancher2_cluster" "my-eks-to-import" {
 
 You can find additional examples for other cloud providers in the https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster[Rancher2 Terraform Provider documentation].
 
-[#_management_capabilities_for_registered_clusters]
+[#management-capabilities-for-registered-clusters]
 == Management Capabilities for Registered Clusters
 
 The control that Rancher has to manage a registered cluster depends on the type of cluster.
 
-* <<_features_for_all_registered_clusters,Features for All Registered Clusters>>
-* <<_additional_features_for_registered_rke2_and_k3s_clusters,Additional Features for Registered RKE2 and K3s Clusters>>
+* <<features-for-all-registered-clusters,Features for All Registered Clusters>>
+* <<additional-features-for-registered-rke2-and-k3s-clusters,Additional Features for Registered RKE2 and K3s Clusters>>
 ifeval::["{build-type}" != "srfa"]
-* <<_additional_features_for_registered_eks_aks_and_gke_clusters,Additional Features for Registered EKS, AKS and GKE Clusters>>
+* <<additional-features-for-registered-eks-aks-and-gke-clusters,Additional Features for Registered EKS, AKS and GKE Clusters>>
 endif::[]
 ifeval::["{build-type}" == "srfa"]
 * <<_additional_features_for_registered_eks_clusters,Additional Features for Registered EKS Clusters>>
 endif::[]
 
-[#_features_for_all_registered_clusters]
+[#features-for-all-registered-clusters]
 === Features for All Registered Clusters
 
 After registering a cluster, the cluster owner can:
@@ -174,23 +174,23 @@ After registering a cluster, the cluster owner can:
 * Enable link:https://documentation.suse.com/cloudnative/rancher-manager/v2.13/en/observability/istio/istio.html[Istio]
 * Manage projects and workloads
 
-[#_additional_features_for_registered_rke2_and_k3s_clusters]
+[#additional-features-for-registered-rke2-and-k3s-clusters]
 === Additional Features for Registered {rke2} and {k3s} Clusters
 
 https://documentation.suse.com/cloudnative/k3s/latest/en/introduction.html[K3s] is a lightweight, fully compliant Kubernetes distribution for edge installations.
 
 https://documentation.suse.com/cloudnative/rke2/latest/en/introduction.html[RKE2] is Rancher's next-generation Kubernetes distribution for datacenter and cloud installations.
 
 When an RKE2 or K3s cluster is registered in Rancher, Rancher will recognize it.
-The Rancher UI will expose features available to <<_features_for_all_registered_clusters,all registered clusters>>, along with the following options for editing and upgrading the cluster:
+The Rancher UI will expose features available to <<features-for-all-registered-clusters,all registered clusters>>, along with the following options for editing and upgrading the cluster:
 
-* Enable or disable <<_configuring_version_management_for_suse_rancher_prime_rke2_and_suse_rancher_prime_k3s_clusters,version management>>
+* Enable or disable <<configuring-version-management-for-suse-rancher-prime-rke2-and-suse-rancher-prime-k3s-clusters,version management>>
 * link:https://documentation.suse.com/cloudnative/rancher-manager/v2.13/en/cluster-admin/backups-and-restore/backups-and-restore.html[Upgrade the Kubernetes version] when version management is enabled
-* Configure the <<_configuring_suse_rancher_prime_rke2_and_suse_rancher_prime_k3s_cluster_upgrades,upgrade strategy>> when version management is enabled
+* Configure the <<configuring-suse-rancher-prime-rke2-and-suse-rancher-prime-k3s-cluster-upgrades,upgrade strategy>> when version management is enabled
 * View a read-only version of the cluster’s configuration arguments and environment variables used to launch each node
 
 ifeval::["{build-type}" != "srfa"]
-[#_additional_features_for_registered_eks_aks_and_gke_clusters]
+[#additional-features-for-registered-eks-aks-and-gke-clusters]
 === Additional Features for Registered EKS, AKS, and GKE Clusters
 
 Rancher handles registered EKS, AKS, or GKE clusters similarly to clusters created in Rancher. However, Rancher doesn't destroy registered clusters when you delete them through the Rancher UI.
@@ -209,7 +209,7 @@ endif::[]
 
 See link:https://documentation.suse.com/cloudnative/rancher-manager/v2.13/en/cluster-deployment/cluster-deployment.html[Cluster Management Capabilities by Cluster Type] for more information about what features are available for managing registered clusters.
 
-[#_configuring_version_management_for_suse_rancher_prime_rke2_and_suse_rancher_prime_k3s_clusters]
+[#configuring-version-management-for-suse-rancher-prime-rke2-and-suse-rancher-prime-k3s-clusters]
 == Configuring Version Management for {rke2} and {k3s} Clusters
 
 [WARNING]
@@ -233,7 +233,7 @@ If version management is enabled for a cluster, Rancher will deploy the `system-
 If version management is disabled, Rancher will remove these components from the cluster.
 ====
 
-[#_configuring_suse_rancher_prime_rke2_and_suse_rancher_prime_k3s_cluster_upgrades]
+[#configuring-suse-rancher-prime-rke2-and-suse-rancher-prime-k3s-cluster-upgrades]
 == Configuring {rke2} and {k3s} Cluster Upgrades
 
 [TIP]