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

Confirm when each exercise is finished.

Browse Source
This commit is contained in:
James Blair
2023-12-07 11:43:21 +13:00
parent ed62fc36e3
commit 3e2fc9b371
6 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
data/workshop/exercise1.mdx
View File

@ -188,3 +188,4 @@ That's a quick introduction to the `oc` command line utility. Let's close our we
| *Closing your web terminal* | | *Closing your web terminal* |
</Zoom> </Zoom>
Well done, you've finished exercise 1! 🎉

1
data/workshop/exercise2.mdx
View File

@ -128,3 +128,4 @@ How much cpu and memory is your ParksMap application currently using?
| *Checking the ParksMap application resource usage* | | *Checking the ParksMap application resource usage* |
</Zoom> </Zoom>
Well done, you've finished exercise 2! 🎉

2
data/workshop/exercise3.mdx
View File

@ -113,3 +113,5 @@ pod "parksmap-ff7477dc4-2nxd2" deleted
If we now run `oc get pods` again we will see a new **Pod** has automatically been created by OpenShift to replace the one we fully deleted. This is because OpenShift is a container orchestration engine that will always try and enforce the desired state that we declare. If we now run `oc get pods` again we will see a new **Pod** has automatically been created by OpenShift to replace the one we fully deleted. This is because OpenShift is a container orchestration engine that will always try and enforce the desired state that we declare.
In our ParksMap **Deployment** we have declared we always want two replicas of our application running at all times. Even if we (possibly accidentally) delete one, OpenShift will always attempt to self heal to return to our desired state. In our ParksMap **Deployment** we have declared we always want two replicas of our application running at all times. Even if we (possibly accidentally) delete one, OpenShift will always attempt to self heal to return to our desired state.
Well done, you've finished exercise 3! 🎉

1
data/workshop/exercise4.mdx
View File

@ -131,3 +131,4 @@ Enter the `gitea` confirmation at the prompt and click **Delete**. If you now re
| *Deleting the gitea application helm release* | | *Deleting the gitea application helm release* |
</Zoom> </Zoom>
Well done, you've finished exercise 4! 🎉

2
data/workshop/exercise5.mdx
View File

@ -135,5 +135,5 @@ Once the new tab opens we should be able to login to Grafana using the credentia
| *Confirming the grafana route is working* | | *Confirming the grafana route is working* |
</Zoom> </Zoom>
Well done, you've finished exercise 5! 🎉

2
data/workshop/exercise6.mdx
View File

@ -88,3 +88,5 @@ After the build has completed and successfully:
- The ReplicaSet will detect no Pods are running and will cause one to be deployed, as our default replica count is just 1. - The ReplicaSet will detect no Pods are running and will cause one to be deployed, as our default replica count is just 1.
To conclude, when issuing the `oc get pods` command, you will see that the build **Pod** has finished (exited) and that an application **Pod** is in a ready and running state. To conclude, when issuing the `oc get pods` command, you will see that the build **Pod** has finished (exited) and that an application **Pod** is in a ready and running state.
Well done, you've finished exercise 6! 🎉