Initial Commit for Learning Paths

prereqs.adoc → 01-path-basics/101-start-here/readme.adoc

@@ -1,5 +1,8 @@
 = Kubernetes Workshop Prereqs
 :toc:
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 Here are the pre-requisites for the link:readme.adoc[Kubernetes on AWS workshop]:
 

cluster-install/readme.adoc → 01-path-basics/102-your-first-cluster/readme.adoc

@@ -1,5 +1,8 @@
 = Create A Kubernetes Cluster Using kops
 :toc:
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 This tutorial will walk you through how to install a Kubernetes cluster on AWS using kops.
 

developer-concepts/readme.adoc → 01-path-basics/103-kubernetes-concepts/readme.adoc

@@ -1,6 +1,8 @@
 = Kubernetes Developer Concepts
 :toc:
-:imagesdir: ../images
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 Kubernetes has a number of abstractions that map to API objects. These Kubernetes API Objects can be used to describe your cluster's desired state which will include info such as applications and workloads running, replicas, container images, networking resources and more. This section explains the key concepts relevant from an application developer perspecitve.
 

developer-concepts/templates/deployment.yaml → 01-path-basics/103-kubernetes-concepts/templates/deployment.yaml

@@ -1,17 +1,17 @@
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  replicas: 3 
-  template:
-    metadata:
-      labels:
-        app: nginx 
-    spec:
-      containers:
-      - name: nginx 
-        image: nginx:1.12.1
-        ports: 
-        - containerPort: 80
-        - containerPort: 443
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: nginx-deployment
+spec:
+  replicas: 3 
+  template:
+    metadata:
+      labels:
+        app: nginx 
+    spec:
+      containers:
+      - name: nginx 
+        image: nginx:1.12.1
+        ports: 
+        - containerPort: 80
+        - containerPort: 443

developer-concepts/templates/echo-deployment.yaml → 01-path-basics/103-kubernetes-concepts/templates/echo-deployment.yaml

@@ -1,17 +1,17 @@
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: echo-deployment 
-spec:
-  replicas: 3 
-  template:
-    metadata:
-      labels:
-        app: echo-pod
-    spec:
-      containers:
-      - name: echoheaders 
-        image: gcr.io/google_containers/echoserver:1.4
-        imagePullPolicy: IfNotPresent 
-        ports: 
-        - containerPort: 8080
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: echo-deployment 
+spec:
+  replicas: 3 
+  template:
+    metadata:
+      labels:
+        app: echo-pod
+    spec:
+      containers:
+      - name: echoheaders 
+        image: gcr.io/google_containers/echoserver:1.4
+        imagePullPolicy: IfNotPresent 
+        ports: 
+        - containerPort: 8080

developer-concepts/templates/echo.yaml → 01-path-basics/103-kubernetes-concepts/templates/echo.yaml

@@ -1,17 +1,17 @@
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: echo-deployment 
-spec:
-  replicas: 3 
-  template:
-    metadata:
-      labels:
-        app: echo-pod
-    spec:
-      containers:
-      - name: echoheaders 
-        image: gcr.io/google_containers/echoserver:1.4
-        imagePullPolicy: IfNotPresent 
-        ports: 
-        - containerPort: 8080
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: echo-deployment 
+spec:
+  replicas: 3 
+  template:
+    metadata:
+      labels:
+        app: echo-pod
+    spec:
+      containers:
+      - name: echoheaders 
+        image: gcr.io/google_containers/echoserver:1.4
+        imagePullPolicy: IfNotPresent 
+        ports: 
+        - containerPort: 8080

developer-concepts/templates/replicaset.yaml → 01-path-basics/103-kubernetes-concepts/templates/replicaset.yaml

@@ -1,18 +1,18 @@
-apiVersion: extensions/v1beta1
-kind: ReplicaSet
-metadata:
-  name: nginx-replicaset
-spec:
-  replicas: 3 
-  template:
-    metadata:
-      labels:
-        name: nginx-replica
-    spec:
-      containers:
-      - name: nginx-replica 
-        image: nginx:1.12.1 
-        imagePullPolicy: IfNotPresent
-        ports:
-        - containerPort: 80
-        - containerPort: 443
+apiVersion: extensions/v1beta1
+kind: ReplicaSet
+metadata:
+  name: nginx-replicaset
+spec:
+  replicas: 3 
+  template:
+    metadata:
+      labels:
+        name: nginx-replica
+    spec:
+      containers:
+      - name: nginx-replica 
+        image: nginx:1.12.1 
+        imagePullPolicy: IfNotPresent
+        ports:
+        - containerPort: 80
+        - containerPort: 443

developer-concepts/templates/service.yaml → 01-path-basics/103-kubernetes-concepts/templates/service.yaml

@@ -1,13 +1,13 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: echo-service
-spec:
-  selector:
-    app: echo-pod
-  ports:
-  - name: http
-    protocol: TCP
-    port: 80
-    targetPort: 8080
+apiVersion: v1
+kind: Service
+metadata:
+  name: echo-service
+spec:
+  selector:
+    app: echo-pod
+  ports:
+  - name: http
+    protocol: TCP
+    port: 80
+    targetPort: 8080
   type: LoadBalancer

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

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../images
+:imagesdir: ../resources/images
 
 == Introduction
 

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

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../images
+:imagesdir: ../resources/images
 
 In this section, we will demonstrate how to integrate service mesh components with a Kubernetes cluster.
 Service mesh is a layer that manages communication between microservices and it is becoming

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

@@ -1,5 +1,8 @@
 = Upgrading Kubernetes cluster
 :toc:
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 Upgrading Kubernetes cluster on AWS is easy with kops. In this exercise we will demonstrate upgrading
 Kubernetes cluster using two methods.

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

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../images
+:imagesdir: ../resources/images
 
 There are many options for aggregating and streaming kubernetes logs. In this part of the workshop, we are going to focus on an AWS based deployment which consists of the following:
 

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

@@ -1,7 +1,8 @@
 = Kubernetes Cluster Auto-scaling
 :toc:
-:imagesdir: ../images
-
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 This tutorial will walk you through how to setup cluster scaling using `cluster-autoscaler` to enable worker node autoscaling based on multiple metrics within Kubernetes.
 
 == Prerequisites

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

@@ -1,4 +1,8 @@
 = Create Kubernetes cluster using CloudFormation and Terraform
+:toc:
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 This chapter explains how to create a Kubernetes cluster using CloudFormation and Terraform.
 

federate-clusters/readme.adoc → 02-path-working-with-clusters/207-cluster-federation/readme.adoc

@@ -1,5 +1,8 @@
 = Setup kubernetes cluster federation on AWS
 :toc:
+:icons:
+:linkcss:
+:imagesdir: ../resources/images
 
 There are many use cases for configuring k8s cluster federation. Most important is high availability
 across AWS regions (also same regions) but this approach can also be applied to hybrid use cases. In this exercise,

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

@@ -1,8 +1,8 @@
 = Kubernetes - Setup Local Development Environment
+:toc:
 :icons:
 :linkcss:
-:imagesdir: ../images
-:toc:
+: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.

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

@@ -1,8 +1,8 @@
 = Service Discovery for Microservices with Kubernetes
+:toc:
 :icons:
 :linkcss:
-:imagesdir: ../images
-:toc:
+: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.
 

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

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../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.
 

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

@@ -2,7 +2,7 @@
 :toc:
 :icons:
 :linkcss:
-:imagesdir: ../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.
 

app-tracing/readme.adoc → 03-path-application-development/305-app-tracing-with-jaeger-and-x-ray/readme.adoc

@@ -1,7 +1,8 @@
 = Application tracing
 :toc:
+:icons:
 :linkcss:
-:imagesdir: ../images
+:imagesdir: ../resources/images
 
 This section will explain how to perform distribute tracing on applications deployed on Kubernetes.