OSDOCS-9085: Adding attributes and IDs to custom domain tutorial

Author: laubai

cloud_experts_tutorials/cloud-experts-rosa-osd-change-default-domain.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="cloud-experts-changing-domains-and-certificates-on-rosa-and-osd"]
+[id="cloud-experts-rosa-osd-change-default-domain"]
 = Tutorial: Changing the Console, OAuth, and Downloads domains and TLS certificate on ROSA and OSD
 include::_attributes/attributes-openshift-dedicated.adoc[]
-:context: cloud-experts-domains-and-certs
+:context: cloud-experts-rosa-osd-change-default-domain
 
 toc::[]
 
@@ -25,12 +25,15 @@ toc::[]
 //Article text
 This guide demonstrates how to modify the Console, Downloads, OAuth domain, and TLS certificate keypair on Red Hat Openshift on AWS (ROSA) and Red Hat Openshift Dedicated (OSD) versions 4.14 and above. {fn-supported-versions}
 
+//// 
 The changes that we make to the component routes {fn-term-component-routes} in this guide are described in greater detail in the following documentation:
 
 * link:https://docs.openshift.com/container-platform/latest/authentication/configuring-internal-oauth.html#customizing-the-oauth-server-url_configuring-internal-oauth[Customizing the internal OAuth server URL]
 * link:https://docs.openshift.com/container-platform/latest/web_console/customizing-the-web-console.html#customizing-the-console-route_customizing-web-console[Customizing the console route]
 * link:https://docs.openshift.com/container-platform/latest/web_console/customizing-the-web-console.html#customizing-the-download-route_customizing-web-console[Customizing the download route]
+//// 
 
+[id="prerequisites_{context}"]
 == Prerequisites
 
 * ROSA CLI (`rosa`) version 1.2.27 or higher {fn-supported-cli}
@@ -40,6 +43,7 @@ The changes that we make to the component routes {fn-term-component-routes} in t
 * OpenSSL (for generating the demonstration SSL certificate), which can be downloaded and installed from link:https://www.openssl.org/source/[OpenSSL.org]
 * Access to the cluster as a user with the `cluster-admin` role.
 
+[id="find-current-routes_{context}"]
 == Find the current routes
 
 Before we make any configuration changes, we need to know the current routes in the cluster.
@@ -104,7 +108,8 @@ If we choose a new base domain of `my-new-domain.dev`, our new component routes
 * `downloads-openshift-console.my-new-domain.dev` for Downloads
 * `oauth-openshift.my-new-domain.dev` for OAuth
 
-== Creating a valid TLS certificate for each component route
+[id="create-tls-certificate-for-routes_{context}"]
+== Create a valid TLS certificate for each component route
 
 In this section, we create a self-signed certificate key pair and then trust it to verify that we can access our new component routes using a real web browser. This is for demonstration purposes only, and is not recommended as a solution for production workloads. Consult your certificate authority to understand how to create a certificate with similar attributes for your production workloads.
 
@@ -136,7 +141,8 @@ $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 365 -keyout key-my-new-do
 
 This generates two `.pem` files, `key-my-new-domain.pem` and `cert-my-new-domain.pem`.
 
-== Adding the certificate to the cluster as a secret
+[id="add-certificate-as-cluster-secret_{context}"]
+== Add the certificate to the cluster as a secret
 
 . Log in to the cluster as a user with the `cluster-admin` role.
 
@@ -149,6 +155,7 @@ This becomes your secret reference when you update the component routes later in
 $ oc create secret tls component-tls --cert=cert-my-new-domain.pem --key=key-my-new-domain.pem -n openshift-config
 ----
 
+[id="find-lb-hostname_{context}"]
 == Find the hostname of the load balancer in your cluster
 
 When you create a cluster, ROSA and OSD create a load balancer and generate a hostname for that load balancer. We need to know the load balancer hostname in order to create DNS records for our cluster.
@@ -166,13 +173,15 @@ In our case, the hostname is `a234gsr3242rsfsfs-1342r624.us-east-1.elb.amazonaws
 
 Save this value for later, as we will need it to configure DNS records for our new component route hostnames.
 
+[id="add-routes-to-dns_{context}"]
 == Add component route DNS records to your hosting provider
 
 In your hosting provider, add DNS records that map the `CNAME` of your new component route hostnames to the load balancer hostname we found in the previous step.
 
 //.Need an image for this
 //image::[Picture goes here]
 
+[id="update-routes-tls-using-rosa-cli_{context}"]
 == Update the component routes and TLS secret using the ROSA CLI
 
 When your DNS records have been updated, you can use the ROSA CLI to change the component routes.