Merge pull request #159 from jhirvioja/update2

Update material #2

data/part-3/1-introduction-to-gke.md

@@ -54,13 +54,11 @@ We can now create a cluster, with the command [gcloud container clusters create]
 
 ```console
 $ gcloud container clusters create dwk-cluster --zone=europe-north1-b --cluster-version=1.29
-ERROR: (gcloud.container.clusters.create) ResponseError: code=403, message=Permission denied on resource project dwk-gke
 
-
-ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=Failed precondition when calling the ServiceConsumerManager: tenantmanager:: Consumer should enable service:container.googleapis.com before generating a service account.
+ERROR: (gcloud.container.clusters.create) ResponseError: code=403, message=Kubernetes Engine API has not been used in project dwk-gke-xxxxxx before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/container.googleapis.com/overview?project=dwk-gke-xxxxxx then retry.
 ```
 
-Let's enable the service in question, `container.googleapis.com`, before retrying.
+You can visit the link that was provided and enable the Kubernetes Engine API, just note that the url which is outputted is specific to your project name. Or, you can just execute the following command on the cli:
 
 ```console
 $ gcloud services enable container.googleapis.com

data/part-3/2-deployment-pipeline.md

@@ -274,7 +274,7 @@ Last step is the deployment. We'll setup Kustomize first:
 ```yaml
 # ...
 - name: Set up Kustomize
-  uses: imranismail/[email protected]
+  uses: imranismail/[email protected].0
 ```
 
 Now we can use Kustomize to set the image we want the pipeline to publish. Here I pipe the output of `kustomize build .` to `kubectl apply`, if you are unsure what is happening you can output the `kustomize build .` and check what was built in the middle of the pipeline!

data/part-4/1-update-strategies-and-prometheus.md

@@ -138,7 +138,7 @@ better option is to use e.g. [ingress-nginx](https://github.com/kubernetes/ingre
 Using _ingress-nginx_ is easy. First, it needs to be installed by running the following commands:
 
 ```bash
-$ repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
+$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
 $ helm repo update
 $ helm install nginx-ingress ingress-nginx/ingress-nginx
 ```
@@ -154,7 +154,7 @@ spec:
   ingressClassName: nginx # this is added
   rules:
   - http:
-      # tules are here
+      # rules are here
 ```
 
 The available ingress controllers (besides the default) can be checked with _kubectl_ as follows:

data/part-5/3-service-mesh.md

@@ -177,6 +177,6 @@ Write an app that serves Wikipedia pages. The app should contain
 - init container that curls page <https://en.wikipedia.org/wiki/Kubernetes> and saves the page content to the public www directory for the main container
 - a sidecar container that waits for a random time between 5 and 15 minutes, curls for a random Wikipedia page in URL  <https://en.wikipedia.org/wiki/Special:Random> and saves the page content to the public www directory for the main container
 
-Hint: you might need to refresh your memory by reading [this](http://localhost:8000/part-1/4-introduction-to-storage#volumes) from part 2 of the course.
+Hint: you might need to refresh your memory by reading [this](/part-1/4-introduction-to-storage#volumes) from part 1 of the course.
 
 </exercise>

data/part-5/4-beyond-kubernetes.md

@@ -42,7 +42,7 @@ Knative has its own community-backed [runtime contract](https://github.com/knati
 
 <exercise name='Exercise 5.06: Trying Serverless'>
 
-Install Knative Serving component to your kd3 cluster.
+Install Knative Serving component to your k3d cluster.
 
 For Knative to work locally in k3d you need to create it a cluster without Traefik: