You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/1-the-manual-menace/1-the-basics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@
46
46
8. Check if you can connect to OpenShift. Run the command below.
47
47
48
48
<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'
Copy file name to clipboardExpand all lines: docs/1-the-manual-menace/2-argocd.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ When something is seen as not matching the required state in Git, an application
29
29
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:
30
30
31
31
<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.
33
33
</p>
34
34
35
35
```bash
@@ -98,15 +98,15 @@ When something is seen as not matching the required state in Git, an application
98
98
⛷️ <b>NOTE</b> ⛷️ - It's also worth noting we're allowing ArgoCD to run in a fairly permissive mode forthese exercise, it can pull charts from anywhere. If you're interestedin 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.
99
99
</p>
100
100
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.
102
102
103
103
```bash
104
104
oc get pods -w -n ${TEAM_NAME}-ci-cd
105
105
```
106
106
107
107

108
108
109
-
*You cando Control+C to break the 'watch' mode*
109
+
*You mustdo Control+C to break the 'watch' mode to continue to the next step. Once all your pods are running*
110
110
111
111
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.
112
112
@@ -151,4 +151,4 @@ When something is seen as not matching the required state in Git, an application
151
151
echo https://$(oc get route/our-todolist -n ${TEAM_NAME}-ci-cd --template='{{.spec.host}}')
152
152
```
153
153
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 🪄🪄
0 commit comments