Next page links

Added links to the next page, to assist navigation directly through github

101-lab/content/00_overview.md

@@ -27,3 +27,5 @@ This course has been completely redesigning and will more than likely have its f
 While we love the idea of everyone getting their hands onto Openshift. The individuals that will get the most value out of the workshop are members that will be performing active developement in Openshift. This includes Application Development as well as Operational Management. The course is __very technical__.
 
 __Please be aware the throughout the labs, you will be guided to make common mistakes, and then guide you on how to fix them.__
+
+Next page - [Setup](./01_adding_team_members.md)

101-lab/content/01_adding_team_members.md

@@ -42,4 +42,6 @@ oc policy add-role-to-user [role] [username]
 
 - Edit: This is the primary role required for developers/devops to do work in a project. It allows the creation/edit/deletion of Openshift Objects including __Secrets__
 
-- View: This is the basic role that provides users with read access to your project. __Secrets are not viewable__ with this privilege.
+- View: This is the basic role that provides users with read access to your project. __Secrets are not viewable__ with this privilege.
+
+Next page - [OCP4 Web Console](./01b_web_console_overview.md)

101-lab/content/01_setup.md

@@ -65,3 +65,5 @@ In addition, developers require GIT locally installed and must have a 2FA device
 ## Command Line Interfaces
 
 You will find many examples `commands` and _tricks_ that highly depend on your OS. These commands were developed on __unix__ based systems. Window's __Command Prompt__ will not work with these examples. You will need to either use __WSL__, __Powershell__, __Gitbash__, or similar.
+
+Next page - [Adding User Access](./01_adding_team_members.md)

101-lab/content/01b_web_console_overview.md

@@ -25,4 +25,6 @@ required to deploy a project
 
 
 
-During this workshop you will be interacting with both views.
+During this workshop you will be interacting with both views.
+
+Next page - [Builds](./02_builds.md)

101-lab/content/02_builds.md

@@ -70,3 +70,5 @@ oc -n [-tools] status
 ![](./images/01_build_logs.png)
 ![](./images/01_build_logs_02.png)
 ![](./images/01_build_logs_03.png)
+
+Next page - [Deployment](./03_deployment.md)

101-lab/content/03_deployment.md

@@ -318,4 +318,4 @@ oc -n [-dev] set probe deployment/rocketchat-[username] --readiness --get-url=ht
 
 You added a __readiness__ check to the `rocketchat-[username]` deployment so that you no longer have a false positive of when the pod should be considered available. By default pods are considered to be 'ready' when the container starts up and the entrypoint script is running. This however is not useful for things like webservers or databases! Not only do you need the entrypoint script to run but you need to wait for the server to listen on a port. 
 
-
+Next page - [Configuring Deployments](./04_configuring_deployments.md)

101-lab/content/04_configuring_deployments.md

@@ -7,7 +7,7 @@ Additional actions are available to edit your deployment configuration. Review a
 ## Using `oc explain`
 
 `oc explain` is a great utility to discover all the available fields for an
-Openshift of K8s object. 
+OpenShift of K8s object. 
 
 - Discover the fields that belong to a Deployment
   - `oc explain deployment`
@@ -36,3 +36,4 @@ cutting over traffic and terminating the previous container.
   - Go back to topology and observe the behaviour. You should notice that the old pod is killed before a new one is created.
   - edit the YAML and switch the strategy back to RollingUpdate
 
+Next page - [Resource Management](./05_resource_management.md)

101-lab/content/05_resource_management.md

@@ -61,4 +61,6 @@ oc -n [-dev] set resources deployment/rocketchat-[username] --requests=cpu=150m,
 
 ## Troubleshooting OOM
 
-The dreaded `OOM` or Out of Memory is when your pods are utilizing less memory than is required for the containers inside of the pod to work. Often there are __no logs__ visible during these issues. Often the symptoms of OOM are `CrashLoop Back off` failure events as well as `rollout` failures. These can be investigated in the `Events` panel. To resolve this you can first increase memory utilization. After that you should investigate if the memory utilization fix is a band-aid or not. In other words, is the application consuming more memory than it should.
+The dreaded `OOM` or Out of Memory is when your pods are utilizing less memory than is required for the containers inside of the pod to work. Often there are __no logs__ visible during these issues. Often the symptoms of OOM are `CrashLoop Back off` failure events as well as `rollout` failures. These can be investigated in the `Events` panel. To resolve this you can first increase memory utilization. After that you should investigate if the memory utilization fix is a band-aid or not. In other words, is the application consuming more memory than it should.
+
+Next page - [Application Availability](./06_application_availability.md) 

101-lab/content/06_application_availability.md

@@ -96,3 +96,5 @@ oc -n [-dev] get pods -o wide | grep rocketchat-[username]
   ```
 - **Windows**
     Windows users can skip the 'watch' steps and monitor their pods from the OpenShift console.
+
+Next page - [Autoscaling](./07_autoscaling.md)

101-lab/content/07_autoscaling.md

@@ -42,3 +42,4 @@ oc -n [-dev] autoscale deployment/rocketchat-[username] --min 1 --max 10 --cpu-p
   ```oc:cli
   oc -n [-dev] delete hpa/rocketchat-[username]
   ```
+Next page - [Persistent Storage](./08_persistent_storage.md)

101-lab/content/08_persistent_storage.md

@@ -166,3 +166,4 @@ To fix that we will need to replace the `RWX` PVC with a `RWO` PVC and change th
     ```oc:cli
     oc -n [-dev] delete pvc/mongodb-[username]-file-rwx
     ```
+Next page - [Persistent Configurations](./09_persistent_configurations.md)

101-lab/content/09_persistent_configurations.md

@@ -157,3 +157,5 @@ With `oc edit`
 
  
 - Redeploy the application after secret changes
+
+Next page - [Event Streams](./10_event_streams.md)

101-lab/content/10_event_streams.md

@@ -22,3 +22,5 @@ oc get events --sort-by='.lastTimestamp'
 
 - Navigate through some of the events and review some of the output that could be helpful 
 in debugging pods
+
+Next page - [Debugging Containers](./11_debugging_containers.md)

101-lab/content/11_debugging_containers.md

@@ -80,3 +80,5 @@ oc -n [-dev] port-forward [pod name from above] 8000:3000
 ```
 
 - Navigate to http://127.0.0.1:8000
+
+Next page - [Logging and Visualizations](./12_logging_and_visualizations.md)

101-lab/content/12_logging_and_visualizations.md

@@ -56,3 +56,5 @@ The shortcut towards accessing the Kibana is from the `Logs` tab of a running po
   ```sql
     kubernetes.namespace_name:"<namespace_name>" AND level:error
   ```
+
+Next page - [Metrics](./13_metrics.md)

101-lab/content/13_metrics.md

@@ -1,9 +1,11 @@
-# Openshift 4 Metrics
+# OpenShift 4 Metrics
 > this feature is in tech preview. This means that it is operational but is not supported under any commercial Service Level Agreement 
 
-Openshift 4 provides a more indepth way to surface metrics for your workloads. These metrics are queries using `PromQL`. 
+OpenShift 4 provides a more indepth way to surface metrics for your workloads. These metrics are queries using `PromQL`. 
 
 ## Running a Sample Metric Query
 
 - Navigate to your __dev namespace__ and select `Observe -> Metrics`
 - Select an sample query provided `CPU Usage` and observe the cpu utilization of your pods
+
+Next page - [Cheat Sheet](./14_cheatsheet.md)