Merge pull request aws-samples#337 from scottmalkie/master

Add path buttons to 20x, 30x, 40x, and 50x sections; Fix imagesdir links

Author: dalbhanj

02-path-working-with-clusters/201-cluster-monitoring/readme.adoc

@@ -317,3 +317,16 @@ Convenient link for other dashboards are listed below:
 Remove all the installed components:
 
     kubectl delete -f templates/prometheus/prometheus-bundle.yaml
+
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../02-path-working-with-clusters/202-service-mesh]
+|image:button-continue-operations.png[link=../../02-path-working-with-clusters/202-service-mesh]
+|=====

02-path-working-with-clusters/202-service-mesh/readme.adoc

@@ -464,3 +464,16 @@ Some errors may appear in the output when deleting Istio. These are related to I
     kubectl get all
     kubectl get all --namespace istio-system
 
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../02-path-working-with-clusters/203-cluster-upgrades]
+|image:button-continue-operations.png[link=../../02-path-working-with-clusters/203-cluster-upgrades]
+|=====    
+

02-path-working-with-clusters/203-cluster-upgrades/readme.adoc

@@ -288,3 +288,14 @@ Upgrading cluster using blue/green method is considered more conservative in nat
 Availability for your application into account. You would setup two k8s cluster, one with 1.6.10
 version and second with 1.7.2 and migrate your pod deployments and services into new cluster.
 
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../03-path-application-development/302-app-discovery]
+|image:button-continue-operations.png[link=../../02-path-working-with-clusters/204-cluster-logging-with-EFK]
+|=====

02-path-working-with-clusters/204-cluster-logging-with-EFK/readme.adoc

@@ -237,3 +237,15 @@ kubectl delete ns logging
 aws es delete-elasticsearch-domain --domain-name kubernetes-logs
 aws logs delete-log-group --log-group-name kubernetes-logs
 ```
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="1", grid="none", frame="none"]
+|=====
+|image:button-continue-operations.png[link=../../02-path-working-with-clusters/204-cluster-logging-with-EFK]
+|=====
+

02-path-working-with-clusters/205-cluster-autoscaling/readme.adoc

@@ -335,3 +335,13 @@ ip-172-20-44-50.eu-central-1.compute.internal     18m          0%        1076Mi
 ip-172-20-75-132.eu-central-1.compute.internal    27m          1%        1723Mi          44% 
 ```
 
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="1", grid="none", frame="none"]
+|=====
+|image:button-continue-operations.png[link=../../02-path-working-with-clusters/205-cluster-autoscaling]
+|=====

02-path-working-with-clusters/206-cloudformation-and-terraform/readme.adoc

@@ -39,3 +39,15 @@ NOTE: https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/[kubea
 == Terraform
 
 The template and instructions need to be added: https://github.com/arun-gupta/kubernetes-aws-workshop/issues/135
+
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="1", grid="none", frame="none"]
+|=====
+|image:button-continue-operations.png[link=../../04-path-security-and-networking/401-configmaps-and-secrets]
+|=====

03-path-application-development/301-local-development/readme.adoc

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../resources/images
+:imagesdir: ../../resources/images
 
 For local development purposes, you can create a one-node cluster using https://github.com/kubernetes/minikube[Minikube].
 Hosted solutions or cloud-based solutions provide the scalability and higher availability for staging or production purposes.
@@ -297,3 +297,15 @@ The cluster can be shutdown using the following command:
     $ minikube stop
     Stopping local Kubernetes cluster...
     Machine stopped.
+
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="1", grid="none", frame="none"]
+|=====
+|image:button-continue-developer.png[link=../../03-path-application-development/302-app-directory]
+|=====

03-path-application-development/302-app-discovery/readme.adoc

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../resources/images
+:imagesdir: ../../resources/images
 
 This chapter shows an example of how different microservices within an application can use service discovery to locate each other in the infrastructure rather than via hardcoded IP addresses.
 
@@ -137,3 +137,15 @@ Delete the application with this command:
 
   $ kubectl delete -f templates/app.yml
 
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../03-path-application-development/303-app-update]
+|image:button-continue-developer.png[link=../../03-path-application-development/303-app-update]
+|=====

03-path-application-development/303-app-update/readme.adoc

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../resources/images
+:imagesdir: ../../resources/images
 
 This chapter explains how an application deployed in a Kubernetes cluster can be updated using link:../developer-concepts#deployment[Deployment]. It also explains Canary Deployment of an application.
 
@@ -531,3 +531,14 @@ https://github.com/zalando-incubator/kube-ingress-aws-controller[Kubernetes Ingr
     deployment "app-ingress-controller" created
 
 
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../03-path-application-development/304-app-scaling]
+|image:button-continue-developer.png[link=../../03-path-application-development/304-app-scaling]
+|=====

03-path-application-development/304-app-scaling/readme.adoc

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../resources/images
+:imagesdir: ../../resources/images
 
 https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/[Horizontal Pod Autoscaling] (HPA) is a Kubernetes feature to dynamically increase/decrease the number of pod replicas based on resource utilization metrics.
 
@@ -104,6 +104,18 @@ webapp    Deployment/webapp   0% / 10%   1         10        1         17m
 
 == Cleanup
 
-    kubectl delete hpa webapp
-    kubectl delete deployment load-generator
-    kubectl delete deployment webapp
+    $ kubectl delete hpa/webapp deploy/load-generator deploy/webapp
+
+
+You are now ready to continue on with the workshop!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2", grid="none", frame="none"]
+|=====
+|image:button-continue-standard.png[link=../../05-path-next-steps/502-for-further-reading]
+|image:button-continue-developer.png[link=../../03-path-application-development/305-app-tracing-with-jaeger-and-x-ray]
+|=====
+