From 7e82f96106d2dbd67aa7ed64d30e284efa2ad9d5 Mon Sep 17 00:00:00 2001 From: Laura Hinson Date: Tue, 3 Mar 2026 13:51:45 -0500 Subject: [PATCH] [OSDOCS-18554]: CQA: HCP on AWS: Accessing a hosted cluster --- .../hcp-deploy/hcp-deploy-aws.adoc | 4 +-- modules/hcp-access-hc-aws-hcpcli.adoc | 26 ------------------- modules/hcp-access-hc-aws.adoc | 21 +++------------ modules/hcp-access-pub-hc-aws-cli.adoc | 1 + modules/hcp-access-pub-hc-aws.adoc | 3 ++- 5 files changed, 7 insertions(+), 48 deletions(-) delete mode 100644 modules/hcp-access-hc-aws-hcpcli.adoc diff --git a/hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc b/hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc index 40d2dac07b64..dbacb21b7801 100644 --- a/hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc +++ b/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,7 @@ 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-pub-hc-aws.adoc[leveloffset=+2] diff --git a/modules/hcp-access-hc-aws-hcpcli.adoc b/modules/hcp-access-hc-aws-hcpcli.adoc deleted file mode 100644 index 6a6d00d903a9..000000000000 --- a/modules/hcp-access-hc-aws-hcpcli.adoc +++ /dev/null @@ -1,26 +0,0 @@ -// Module included in the following assemblies: -// -// * hosted-control-planes/hcp-deploy/hcp-deploy-aws.adoc - -:_mod-docs-content-type: PROCEDURE -[id="hcp-access-hc-aws-hcpcli_{context}"] -= Accessing a hosted cluster on {aws-short} by using the hcp CLI - -You can access the hosted cluster by using the `hcp` command-line interface (CLI) to generate the `kubeconfig` file. - -.Procedure - -. Generate the `kubeconfig` file by entering the following command: -+ -[source,terminal] ----- -$ hcp create kubeconfig --namespace \ - --name > .kubeconfig ----- - -. After you save the `kubeconfig` file, you can access the hosted cluster by entering the following command: -+ -[source,terminal] ----- -$ oc --kubeconfig .kubeconfig get nodes ----- diff --git a/modules/hcp-access-hc-aws.adoc b/modules/hcp-access-hc-aws.adoc index 1edf456ea7da..98ca2f53d6c1 100644 --- a/modules/hcp-access-hc-aws.adoc +++ b/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: `--admin-kubeconfig`. For example, `clusters-hypershift-demo-admin-kubeconfig`. -* `kubeadmin` password secret: `--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 .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. \ No newline at end of file diff --git a/modules/hcp-access-pub-hc-aws-cli.adoc b/modules/hcp-access-pub-hc-aws-cli.adoc index 2bb04a7decd9..580de7499bfd 100644 --- a/modules/hcp-access-pub-hc-aws-cli.adoc +++ b/modules/hcp-access-pub-hc-aws-cli.adoc @@ -6,6 +6,7 @@ [id="hcp-access-pub-hc-aws-cli_{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). .Procedure diff --git a/modules/hcp-access-pub-hc-aws.adoc b/modules/hcp-access-pub-hc-aws.adoc index f83ff6c0ab6b..f8ef4f1bc92e 100644 --- a/modules/hcp-access-pub-hc-aws.adoc +++ b/modules/hcp-access-pub-hc-aws.adoc @@ -6,7 +6,8 @@ [id="hcp-access-pub-hc-aws_{context}"] = Accessing a hosted cluster on {aws-short} by using the kubeadmin credentials -After creating a hosted cluster on {aws-first}, you can access a hosted cluster by getting the `kubeconfig` file, access secrets, and the `kubeadmin` credentials. +[role="_abstract"] +After you create a hosted cluster on {aws-first}, you can access it by getting the `kubeconfig` file, access secrets, and the `kubeadmin` credentials. The hosted cluster namespace contains hosted cluster resources and the access secrets. The hosted control plane runs in the hosted control plane namespace.