diff --git a/data/workshop/exercise1.mdx b/data/workshop/exercise1.mdx index adb3d22..46e2c09 100644 --- a/data/workshop/exercise1.mdx +++ b/data/workshop/exercise1.mdx @@ -188,3 +188,4 @@ That's a quick introduction to the `oc` command line utility. Let's close our we | *Closing your web terminal* | +Well done, you've finished exercise 1! 🎉 diff --git a/data/workshop/exercise2.mdx b/data/workshop/exercise2.mdx index f4be9f7..3c8a558 100644 --- a/data/workshop/exercise2.mdx +++ b/data/workshop/exercise2.mdx @@ -128,3 +128,4 @@ How much cpu and memory is your ParksMap application currently using? | *Checking the ParksMap application resource usage* | +Well done, you've finished exercise 2! 🎉 diff --git a/data/workshop/exercise3.mdx b/data/workshop/exercise3.mdx index c1bfb9b..c08eb91 100644 --- a/data/workshop/exercise3.mdx +++ b/data/workshop/exercise3.mdx @@ -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. 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! 🎉 diff --git a/data/workshop/exercise4.mdx b/data/workshop/exercise4.mdx index 7855f43..eca258d 100644 --- a/data/workshop/exercise4.mdx +++ b/data/workshop/exercise4.mdx @@ -131,3 +131,4 @@ Enter the `gitea` confirmation at the prompt and click **Delete**. If you now re | *Deleting the gitea application helm release* | +Well done, you've finished exercise 4! 🎉 diff --git a/data/workshop/exercise5.mdx b/data/workshop/exercise5.mdx index 4222a93..b900ea3 100644 --- a/data/workshop/exercise5.mdx +++ b/data/workshop/exercise5.mdx @@ -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* | - +Well done, you've finished exercise 5! 🎉 diff --git a/data/workshop/exercise6.mdx b/data/workshop/exercise6.mdx index 9222040..64b0b06 100644 --- a/data/workshop/exercise6.mdx +++ b/data/workshop/exercise6.mdx @@ -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. 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! 🎉