From 617fc7bdcc6af788b9368c62ac0c13e197f466f6 Mon Sep 17 00:00:00 2001 From: James Blair Date: Fri, 25 Oct 2024 09:08:33 +1300 Subject: [PATCH] Add hint to exercise 2. --- data/workshop/README.org | 2 +- data/workshop/exercise2.mdx | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/data/workshop/README.org b/data/workshop/README.org index c1d4e01..aaf43b2 100644 --- a/data/workshop/README.org +++ b/data/workshop/README.org @@ -8,7 +8,7 @@ This document captures the steps required to set up an instance of the workshop. * Log in to cluster #+begin_src tmux -oc login --web https://api.cluster-zwm4h.zwm4h.sandbox1572.opentlc.com:6443/ +oc login --web https://api.cluster-pnccw.pnccw.sandbox225.opentlc.com:6443/ #+end_src * Update cluster logo diff --git a/data/workshop/exercise2.mdx b/data/workshop/exercise2.mdx index 149c39b..2762d19 100644 --- a/data/workshop/exercise2.mdx +++ b/data/workshop/exercise2.mdx @@ -52,6 +52,8 @@ Documentation you may find helpful is: Alright, you've given Angie a quick tour around the Red Hat Advanced Cluster Security Console, now it's time to secure this hub cluster by generating an init bundle named `prd-acme-hub` and applying it to the cluster. +You remember from the documentation that before you install the `SecuredCluster` resource on a cluster, you must create an init bundle. The cluster that has `SecuredCluster` resource then uses this bundle to authenticate with Central. + Angie would prefer to use the **Operator** method for these tasks as she explains having repressed memories of trying to find indentation issues in helm chart templates and never ever wanting to touch helm ever again. @@ -83,6 +85,8 @@ Documentation you may find helpful is: | *Secured cluster list in Red Hat Advanced Cluster Security* | +> **Hint** If your SecuredCluster pods are in the right namespace and are not all starting successfully this can commonly occur because you have missed appending the `:443` to your central endpoint in the `SecuredCluster` resource. + ## 2.5 - Check your work