jmhbnz/workshops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add hint to exercise 2.

Browse Source
This commit is contained in:
James Blair
2024-10-25 09:08:33 +13:00
parent 0b061fa8b7
commit 617fc7bdcc
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/workshop/README.org
View File

@ -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

4
data/workshop/exercise2.mdx
View File

@ -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.
<Zoom>
@ -83,6 +85,8 @@ Documentation you may find helpful is:
| *Secured cluster list in Red Hat Advanced Cluster Security* |
</Zoom>
> **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