🎶kcd munich updates

Author: ckavili

docs/1-the-manual-menace/1-the-basics.md

@@ -1,7 +1,7 @@
 ## 🐌 The Basics - CRW, OCP & Helm
 ## DevSpaces setup
 
-1. Login to your DevSpaces Editor here - [https://devspaces.<CLUSTER_DOMAIN>](https://devspaces.<CLUSTER_DOMAIN>). Use the `FREE IPA` login and use the user credentials provided by the instructor. Click `tl500` from the left menu. It will open a new browser tab to take you your IDE.
+1. Login to your DevSpaces Editor here - [https://red.ht/kcdmunich-devspaces](https://red.ht/kcdmunich-devspaces). Use the `FREE IPA` login and use the user credentials provided by the instructor. Click `tl500` from the left menu. It will open a new browser tab to take you your IDE.
 
     ![tl500](./images/tl500.png)
 

docs/1-the-manual-menace/3-ubiquitous-journey.md

@@ -51,16 +51,7 @@ All of these traits lead to one outcome - the ability to build and release quali
 
 ![values-tooling](./images/values-tooling.png)
 
-3. This is GITOPS - so in order to affect change, let's get the configuration into git, before telling ArgoCD to sync the changes for us.
-
-    ```bash#test
-    cd /projects/tech-exercise/
-    git add .
-    git commit -m  "🦆 ADD - bootstrap and nexus 🦆"
-    git push
-    ```
-
-4. In order for ArgoCD to sync the changes from our git repository, we need to provide access to it. We'll deploy a secret to cluster, for now *not done as code* but in the next lab we'll add the secret as code and store it encrypted in Git. In your terminal
+3. In order for ArgoCD to sync the changes from our git repository, we need to provide access to it. We'll deploy a secret to cluster, for now *not done as code* but in the next lab we'll add the secret as code and store it encrypted in Git. In your terminal
 
     Add the Secret to the cluster:
 
@@ -83,6 +74,7 @@ All of these traits lead to one outcome - the ability to build and release quali
       metadata:
         annotations:
           tekton.dev/git-0: https://${GIT_SERVER}
+          sealedsecrets.bitnami.com/managed: "true"
         name: git-auth
 EOF
     ```
@@ -103,4 +95,8 @@ EOF
     oc get projects | grep ${TEAM_NAME}
     ```
 
+    ```bash#test
+    oc get pods -n ${TEAM_NAME}-ci-cd
+    ```
+
 🪄🪄 Magic! You've now deployed an app of apps to scaffold our tooling and projects in a repeatable and auditable way (via git!). Next up, we'll make extend the Ubiquitous Journey with some tooling 🪄🪄

docs/1-the-manual-menace/images/argocd-empty.png

@@ -7,22 +7,22 @@ Sealed Secrets allows us to _seal_ Kubernetes secrets by using a utility called
 
 ### Sealed Secrets in action
 
-1. The observant among you will have noticed that in the previous exercise we created a secret for git and added it to the cluster WITHOUT putting it in git...😳 Lets start by fixing this and sealing our Git credentials so they can be safely checked in to the code. First, we'll create the secret in a tmp directory. Make sure you have your gitlab user and PAT from the previous exercise set in your environment
+1. The observant among you will have noticed that in the previous exercise we created a secret for git and added it to the cluster WITHOUT putting it in git...😳 Lets start by fixing this and sealing our Git credentials so they can be safely checked in to the code. First, we'll create the secret in a tmp directory. Make sure you have your GitLab user and password from the previous exercise set in your environment.
 
     ```bash
     echo ${GITLAB_USER}
-    echo ${GITLAB_PAT}
+    echo ${GITLAB_PASSWORD}
     ```
 
-2. Run this command to generate a Kubernetes secret object in `/tmp` with the right labels needed for Tekton and Jenkins later.
+2. Run this command to generate a Kubernetes secret object in `/tmp` with the right labels needed for Tekton later.
 
     ```bash#test
     cat << EOF > /tmp/git-auth.yaml
     kind: Secret
     apiVersion: v1
     data:
       username: "$(echo -n ${GITLAB_USER} | base64 -w0)"
-      password: "$(echo -n ${GITLAB_PAT} | base64 -w0)"
+      password: "$(echo -n ${GITLAB_PASSWORD} | base64 -w0)"
     type: kubernetes.io/basic-auth
     metadata:
       annotations:

docs/2-attack-of-the-pipelines/1-sealed-secrets.md

@@ -148,10 +148,5 @@ In this snippet of the pipeline used in this exercise, we define:
 
     ![images/tekton-pipeline-running.png](images/tekton-pipeline-running.png)
 
-?> **TIP** You can use the **tkn** command line to observe `PipelineRun` logs as well:
-
-```bash
-tkn -n ${TEAM_NAME}-ci-cd pr logs -Lf
-```
 
 🪄 OBSERVE THE PIPELINE IS RUNNING 🪄