Add GitHub markup

Author: bmuschko

exercises/12-deployment-horizontal-pod-autoscaler/instructions.md

@@ -10,7 +10,7 @@
 </p>
 </details>
 
-> [!NOTE]
+> [!IMPORTANT]
 > You will need to install the metrics server if you want actual resource metrics to be collected and displayed by the HorizontalPodAutoscaler. You can find [installation instructions](https://github.com/kubernetes-sigs/metrics-server#installation) on the project's GitHub page.
 
 1. Create a Deployment named `nginx` with 1 replica. The Pod template of the Deployment should use container image `nginx:1.23.4`, set the CPU resource request to 0.5, and the memory resource request/limit to 500Mi.

exercises/14-helm-consume-chart/instructions.md

@@ -12,7 +12,7 @@
 
 In this exercise, you use Helm to install Kubernetes objects needed for the open source monitoring solution [Prometheus](https://prometheus.io/). The easiest way to install Prometheus on top of Kubernetes is with the help of the [prometheus-operator](https://prometheus-operator.dev/) Helm chart.
 
-> [!NOTE]
+> [!IMPORTANT]
 > You will need to have Helm installed on your machine. The Helm documentation page provides detailed, OS-specific [installation instructions](https://helm.sh/docs/intro/install/).
 
 1. The Prometheus Helm charts reside in the [artifact repository](https://prometheus-community.github.io/helm-charts). Add the repository to the list of known repositories accessible by Helm with the name `prometheus-community`.

exercises/15-helm-build-chart/instructions.md

@@ -12,6 +12,9 @@
 
 In this exercise, you will practice the implementation, packaging, and installation of a configurable custom Helm chart.
 
+> [!IMPORTANT]
+> You will need to have Helm installed on your machine. The Helm documentation page provides detailed, OS-specific [installation instructions](https://helm.sh/docs/intro/install/).
+
 1. Create a new chart file named `Chart.yaml`. Define all mandatory attributes including the chart's API version, the name, and the version. Add the following key-value pairs: `API version: 1.0.0`, `Name: web-app`, and `Version: 2.5.4`.
 2. Create a new values file named `values.yaml`. It should contain the following key-value pairs: `service_port: 80`, and `container_port: 3000`.
 3. Create the template file `web-app-pod-template.yaml`. The YAML manifest defines a Pod named `hello-world` with the image `bmuschko/nodejs-hello-world:1.0.0`. The container port uses the placeholder `container_port` from the `values.yaml` file.

exercises/18-pod-metrics/instructions.md

@@ -10,7 +10,7 @@
 </p>
 </details>
 
-> [!NOTE]
+> [!IMPORTANT]
 > You will need to install the metrics server if you want to be able to inspect actual resource metrics. You can find [installation instructions](https://github.com/kubernetes-sigs/metrics-server#installation) on the project's GitHub page.
 
 1. Create the namespace `stress-test`.

exercises/28-service/instructions.md

@@ -16,7 +16,7 @@ In this exercise, you will create a Deployment and expose a container port for i
 > If you do not already have a cluster, you can create one by using minikube or you can use the O'Reilly interactive labs ["Creating a Service of type ClusterIP"](https://learning.oreilly.com/scenarios/ckad-services-creating/9781098105310/) and ["Creating a Service of type NodePort"](https://learning.oreilly.com/scenarios/ckad-services-creating/9781098105327/).
 
 > [!IMPORTANT]
-> If you are using minikube, the network is limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly. Refer to the [documentation](https://minikube.sigs.k8s.io/docs/handbook/accessing/) to gain access to the minikube IP.
+> If you are using minikube, the network is limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly. Refer to the [documentation](https://minikube.sigs.k8s.io/docs/handbook/accessing/#nodeport-access) to fetch the minikube IP and a service's node port.
 
 1. Create a Service named `myapp` of type `ClusterIP` that exposes port 80 and maps to the target port 80.
 2. Create a Deployment named `myapp` that creates 1 replica running the image `nginx:1.23.4-alpine`. Expose the container port 80.