[OSDOCS-18554]: CQA: HCP on AWS: Accessing a hosted cluster

Author: lahinson

hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc

@@ -17,8 +17,6 @@ include::modules/hcp-aws-prepare.adoc[leveloffset=+1]
 
 include::modules/hcp-aws-prereqs.adoc[leveloffset=+2]
 
-include::modules/hcp-access-hc-aws-hcpcli.adoc[leveloffset=+1]
-
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.15/html/clusters/cluster_mce_overview#ansible-config-hosted-cluster[Configuring Ansible Automation Platform jobs to run on hosted clusters]
@@ -57,7 +55,9 @@ include::modules/hcp-aws-deploy-hc.adoc[leveloffset=+1]
 .Additional resources
 * xref:../../hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc#hcp-enable-arm-amd_hcp-deploy-aws[Running hosted clusters on an ARM64 architecture]
 
-include::modules/hcp-access-hc-aws.adoc[leveloffset=+2]
+include::modules/hcp-access-hc-aws.adoc[leveloffset=+1]
+
+include::modules/hcp-access-hc-aws-hcpcli.adoc[leveloffset=+2]
 
 include::modules/hcp-access-pub-hc-aws.adoc[leveloffset=+2]
 

modules/hcp-access-hc-aws-hcpcli.adoc

@@ -6,6 +6,7 @@
 [id="hcp-access-hc-aws-hcpcli_{context}"]
 = Accessing a hosted cluster on {aws-short} by using the hcp CLI
 
+[role="_abstract"]
 You can access the hosted cluster by using the `hcp` command-line interface (CLI) to generate the `kubeconfig` file.
 
 .Procedure

modules/hcp-access-hc-aws.adoc

@@ -2,24 +2,9 @@
 //
 // * hosted-control-planes/hcp-deploy/hcp-deploy-aws.adoc
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 [id="hcp-access-hc-aws_{context}"]
 = Accessing a hosted cluster on {aws-short}
 
-You can access the hosted cluster by getting the `kubeconfig` file and the `kubeadmin` credentials directly from resources.
-
-You must be familiar with the access secrets for hosted clusters. The hosted cluster namespace contains hosted cluster resources, and the hosted control plane namespace is where the hosted control plane runs. The secret name formats are as follows:
-
-* `kubeconfig` secret: `<hosted-cluster-namespace>-<name>-admin-kubeconfig`. For example, `clusters-hypershift-demo-admin-kubeconfig`.
-* `kubeadmin` password secret: `<hosted-cluster-namespace>-<name>-kubeadmin-password`. For example, `clusters-hypershift-demo-kubeadmin-password`.
-
-.Procedure
-
-* The `kubeconfig` secret contains a Base64-encoded `kubeconfig` field, which you can decode and save into a file to use with the following command:
-+
-[source,terminal]
-----
-$ oc --kubeconfig <hosted_cluster_name>.kubeconfig get nodes
-----
-+
-The `kubeadmin` password secret is also Base64-encoded. You can decode it and use the password to log in to the API server or console of the hosted cluster.
+[role="_abstract"]
+After you create a hosted cluster on {aws-short}, you can access it by using the hosted control plane CLI (`hcp`) or by using `kubeadmin` credentials.