Skip to content

Commit c2728bd

Browse files
committed
2 parents e490e6d + 05f5420 commit c2728bd

File tree

3 files changed

+9
-15
lines changed

3 files changed

+9
-15
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@
4646
8. Check if you can connect to OpenShift. Run the command below.
4747

4848
<p class="tip">
49-
⛷️ <b>TIP</b> ⛷️ - Before you hit enter, make sure you change the username and password to match your team's login details
49+
⛷️ <b>TIP</b> ⛷️ - Before you hit enter, make sure you change the username and password to match your team's login details. If your password includes special characters, put it in single quotes. ie: 'A8y?Rpm!9+A3B/KG'
5050
</p>
5151
5252
```bash

docs/1-the-manual-menace/2-argocd.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ When something is seen as not matching the required state in Git, an application
2929
2. We are using the [Red Hat GitOps Operator](https://github.com/redhat-developer/gitops-operator) which was deployed as part of the cluster setup. Normally this step would be done as part of the Operator Install so its a bit more complicated than we would like. Because _we did not know_ your team names ahead of time 👻 we will need to update an environment variable on the Operator Subscription. This tells the Operator its OK to deploy a cluster scoped ArgoCD instance into your <TEAM_NAME>-ci-cd project. Run this shell script:
3030

3131
<p class="tip">
32-
🐌 THIS IS NOT GITOPS - Until we work out a better way to automate this. 🐎
32+
🐌 THIS IS NOT GITOPS - Until we work out a better way to automate this. 🐎 If you see "...." in your terminal after you copy this shell script, do not worry. Hit return and it will run as designed.
3333
</p>
3434

3535
```bash
@@ -98,15 +98,15 @@ When something is seen as not matching the required state in Git, an application
9898
⛷️ <b>NOTE</b> ⛷️ - It's also worth noting we're allowing ArgoCD to run in a fairly permissive mode for these exercise, it can pull charts from anywhere. If you're interested in securing ArgoCD a bit more, checkout the <span style="color:blue;"><a href="/#/1-the-manual-menace/666-here-be-dragons?id=here-be-dragons">here-be-dragons</a></span> exercise at the end of this lab.
9999
</p>
100100
101-
3. If we check in OpenShift we should see the Operator pod coming to life and (eventually) the argocd-server, dex and other pods spin up.
101+
3. If we check in OpenShift we should see the Operator pod coming to life and (eventually) the argocd-server, dex and other pods spin up. To do this, we are going to run a command with a 'watch' flag to continuousy monitor pod creation.
102102
103103
```bash
104104
oc get pods -w -n ${TEAM_NAME}-ci-cd
105105
```
106106
107107
![argocd-pods](images/argocd-pods.png)
108108
109-
*You can do Control+C to break the 'watch' mode*
109+
*You must do Control+C to break the 'watch' mode to continue to the next step. Once all your pods are running*
110110
111111
4. When all the pods are up and running, we can login to the UI of ArgoCD. Get the route and open it in a new browser tab.
112112
@@ -151,4 +151,4 @@ When something is seen as not matching the required state in Git, an application
151151
echo https://$(oc get route/our-todolist -n ${TEAM_NAME}-ci-cd --template='{{.spec.host}}')
152152
```
153153
154-
🪄🪄 Magic! You've now deployed ArgoCD and got it to manually deploy an application for you. Next up, we'll make ArgoCD do some *REAL* GitOps 🪄🪄
154+
🪄🪄 Magic! You've now deployed ArgoCD and got it to manually deploy an application for you. Next up, we'll make ArgoCD do some *REAL* GitOps 🪄🪄

docs/slides/content/tech-exercise-i.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -87,17 +87,11 @@ _We will set up Git projects, create dev, test, and stage projects in OpenShift,
8787

8888

8989

90-
### 💥 Mob to Learn 💥
91-
* Begin with the [pairing and mobbing](?name=pairing-and-mobbing) exercise (if not already completed).
90+
### 💥 Let's Begin 💥
9291
* In your table teams, form a mob to complete the exercise. Work together as a team to deploy your shared tooling and infrastructure!
93-
* Rotate the `driver` at the end of the section to give everyone a chance to get their hands dirty with code!
94-
* If you finish early, try your hand at the `Here be dragons` section.
95-
* Your tutor will share links to the instructions, OpenShift Console, CRW, and GitLab server.
96-
97-
98-
99-
### 💥 CodeReadyWorkspaces 💥 <!-- .element: class="title-bottom-left" -->
100-
<!-- .slide: data-background-size="contain" data-background-image="images/tech-exercise-i/crw.png", class="white-style" data-background-opacity="1" -->
92+
* You will want to rotate the `driver` at the end of each exercise section to give everyone a chance to get their hands dirty with code!
93+
* If you finish the exercise early, try your hand at the `Here be dragons` section.
94+
* Your facilitator will share links to the instructions, OpenShift Console, CRW, and GitLab server.
10195

10296

10397

0 commit comments

Comments
 (0)