Add buttons to main readme; Re-add Basics to 103

Author: Scott Malkie

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

@@ -1,8 +1,9 @@
 = Kubernetes - Setup Cloud9 Development Environment
+:toc:
 :icons:
 :linkattrs:
 :imagesdir: ../../resources/images
-:toc:
+
 
 This section walks you through the creating a Kubernetes development environment using https://aws.amazon.com/cloud9/[AWS Cloud9].  This will provide you with a cloud-based integrated development environment (IDE) that will let you write, run, and debug containerized workloads using just a web browser.
 

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

@@ -2,10 +2,9 @@
 :toc:
 :icons:
 :linkattrs:
-:linkcss:
 :imagesdir: ../../resources/images
 
-== Kubernetes API and CLI
+== Introduction
 
 Now that we have a cluster up and running we can start exploring the Kubernetes CLI via the `kubectl` (pronounced "cube control") command.
 
@@ -42,6 +41,143 @@ It will show an output similar to:
 
 If you do not see this output, or receive an error, please ensure that you've followed the steps link:../102-your-first-cluster#multi-master[here] and have a validated cluster.
 
+=== Create your first Pod
+
+This command instantiates an nginx container into your cluster, inside a pod:
+
+    $ kubectl run nginx --image=nginx
+    deployment "nginx" created
+
+Get the list of deployments:
+
+    $ kubectl get deployments
+    NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
+    nginx     1         1         1            0           41s
+
+Get the list of running pods:
+
+    $ kubectl get pods
+    NAME                     READY     STATUS    RESTARTS   AGE
+    nginx-4217019353-pmkzb   1/1       Running   0          1m
+
+Get additional details for the pod by using the `<pod-name>` from the above output:
+
+```
+$ kubectl describe pod/nginx-4217019353-pmkzb
+kubectl describe pod/nginx-4217019353-pmkzb
+Name:           nginx-4217019353-pmkzb
+Namespace:      default
+Node:           ip-172-20-87-91.us-east-2.compute.internal/172.20.87.91
+Start Time:     Fri, 01 Dec 2017 16:36:48 -0800
+Labels:         pod-template-hash=4217019353
+                run=nginx
+Annotations:    kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"default","name":"nginx-4217019353","uid":"e161abe9-d6f8-11e7-af8f-06c4465216f2","...
+                kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container nginx
+Status:         Running
+IP:             100.96.7.19
+Created By:     ReplicaSet/nginx-4217019353
+Controlled By:  ReplicaSet/nginx-4217019353
+Containers:
+  nginx:
+    Container ID:   docker://2def6a6dc1594c337748abf6160ff81fab9fa6d734aca02b5f1afc4d395edc6b
+    Image:          nginx
+    Image ID:       docker-pullable://nginx@sha256:b81f317384d7388708a498555c28a7cce778a8f291d90021208b3eba3fe74887
+    Port:           <none>
+    State:          Running
+      Started:      Fri, 01 Dec 2017 16:36:52 -0800
+    Ready:          True
+    Restart Count:  0
+    Requests:
+      cpu:        100m
+    Environment:  <none>
+    Mounts:
+      /var/run/secrets/kubernetes.io/serviceaccount from default-token-cqht0 (ro)
+Conditions:
+  Type           Status
+  Initialized    True
+  Ready          True
+  PodScheduled   True
+Volumes:
+  default-token-cqht0:
+    Type:        Secret (a volume populated by a Secret)
+    SecretName:  default-token-cqht0
+    Optional:    false
+QoS Class:       Burstable
+Node-Selectors:  <none>
+Tolerations:     node.alpha.kubernetes.io/notReady:NoExecute for 300s
+                 node.alpha.kubernetes.io/unreachable:NoExecute for 300s
+Events:
+  Type    Reason                 Age   From                                                 Message
+  ----    ------                 ----  ----                                                 -------
+  Normal  Scheduled              46s   default-scheduler                                    Successfully assigned nginx-4217019353-pmkzb to ip-172-20-87-91.us-east-2.compute.internal
+  Normal  SuccessfulMountVolume  46s   kubelet, ip-172-20-87-91.us-east-2.compute.internal  MountVolume.SetUp succeeded for volume "default-token-cqht0"
+  Normal  Pulling                46s   kubelet, ip-172-20-87-91.us-east-2.compute.internal  pulling image "nginx"
+  Normal  Pulled                 42s   kubelet, ip-172-20-87-91.us-east-2.compute.internal  Successfully pulled image "nginx"
+  Normal  Created                42s   kubelet, ip-172-20-87-91.us-east-2.compute.internal  Created container
+  Normal  Started                42s   kubelet, ip-172-20-87-91.us-east-2.compute.internal  Started container
+
+```
+
+By default, pods are created in a `default` namespace. In addition, a `kube-system` namespace is also reserved for Kubernetes system pods. A list of all the pods in `kube-system` namespace can be displayed as shown:
+
+```
+$ kubectl get pods --namespace kube-system
+NAME                                                                  READY     STATUS    RESTARTS   AGE
+dns-controller-3497129722-4pxd6                                       1/1       Running   0          28d
+etcd-server-events-ip-172-20-124-26.us-east-2.compute.internal        1/1       Running   0          28d
+etcd-server-events-ip-172-20-52-35.us-east-2.compute.internal         1/1       Running   0          28d
+etcd-server-events-ip-172-20-94-153.us-east-2.compute.internal        1/1       Running   0          28d
+etcd-server-ip-172-20-124-26.us-east-2.compute.internal               1/1       Running   0          28d
+etcd-server-ip-172-20-52-35.us-east-2.compute.internal                1/1       Running   0          28d
+etcd-server-ip-172-20-94-153.us-east-2.compute.internal               1/1       Running   0          28d
+kube-apiserver-ip-172-20-124-26.us-east-2.compute.internal            1/1       Running   0          28d
+kube-apiserver-ip-172-20-52-35.us-east-2.compute.internal             1/1       Running   0          28d
+kube-apiserver-ip-172-20-94-153.us-east-2.compute.internal            1/1       Running   0          28d
+kube-controller-manager-ip-172-20-124-26.us-east-2.compute.internal   1/1       Running   0          28d
+kube-controller-manager-ip-172-20-52-35.us-east-2.compute.internal    1/1       Running   0          28d
+kube-controller-manager-ip-172-20-94-153.us-east-2.compute.internal   1/1       Running   0          28d
+kube-dns-1311260920-jgl0m                                             3/3       Running   0          28d
+kube-dns-1311260920-tvpmp                                             3/3       Running   0          28d
+kube-dns-autoscaler-1818915203-5kxrb                                  1/1       Running   0          28d
+kube-proxy-ip-172-20-105-158.us-east-2.compute.internal               1/1       Running   0          28d
+kube-proxy-ip-172-20-124-26.us-east-2.compute.internal                1/1       Running   0          28d
+kube-proxy-ip-172-20-127-251.us-east-2.compute.internal               1/1       Running   0          28d
+kube-proxy-ip-172-20-52-35.us-east-2.compute.internal                 1/1       Running   0          28d
+kube-proxy-ip-172-20-63-150.us-east-2.compute.internal                1/1       Running   0          28d
+kube-proxy-ip-172-20-71-14.us-east-2.compute.internal                 1/1       Running   0          28d
+kube-proxy-ip-172-20-87-91.us-east-2.compute.internal                 1/1       Running   0          28d
+kube-proxy-ip-172-20-94-153.us-east-2.compute.internal                1/1       Running   0          28d
+kube-scheduler-ip-172-20-124-26.us-east-2.compute.internal            1/1       Running   0          28d
+kube-scheduler-ip-172-20-52-35.us-east-2.compute.internal             1/1       Running   0          28d
+kube-scheduler-ip-172-20-94-153.us-east-2.compute.internal            1/1       Running   0          28d
+tiller-deploy-1114875906-k2pj2                                        1/1       Running   0          28d
+```
+Again, the exact output may vary but your results should look similar to these.
+
+=== Get logs from the pod
+
+Logs from the pod can be obtained (a fresh nginx does not have logs - check again later once you have accessed the service):
+
+    $ kubectl logs <pod-name>
+
+=== Execute a shell on the running pod
+
+This command will open a TTY to a shell in your pod:
+
+    $ kubectl get pods
+    $ kubectl exec -it <pod-name> /bin/bash
+
+This opens a bash shell and allows you to look around the filesystem of the container.
+
+=== Clean up
+
+Delete all the Kubernetes resources created so far:
+
+    $ kubectl delete deployment/nginx
+
+
+In the next sections, we will go into more detail about Pods, Deployments, and other commonly used Kubernetes objects.
+
 == Pods
 
 A Pod is the smallest deployable unit that can be created, scheduled, and managed. It’s a logical collection of containers that belong to an application. Pods are created in a namespace. All containers in a pod share the namespace, volumes and networking stack. This allows containers in the pod to "`find`" each other and communicate using `localhost`.

readme.adoc

@@ -1,23 +1,39 @@
-= AWS Workshop for Kubernetes
+= Kubernetes the AWSome Way!
+:icons:
+:linkattrs:
+:imagesdir: resources/images
 
-image:resources/images/kubernetes-aws-smile.png[alt="kubernetes and aws logos", align="left",width=420]
+image:kubernetes-aws-smile.png[alt="kubernetes and aws logos", align="left",width=420]
 
 This is a self-paced workshop designed for Development and Operations teams who would like to leverage Kubernetes on Amazon Web Services (AWS).
 
 This workshop provides instructions to create, manage, and scale a Kubernetes cluster on AWS, as well as how to deploy applications, scale them, run stateless and stateful containers, perform service discovery between different microservices, and other similar concepts.
 
 It also shows deep integration with several AWS technologies.
 
-== Paths
+We recommend at least 2 hours for the standard workshop path.
 
-There are two main paths. Each path should take approximately 4 hours to complete. 
-[cols="2*^"]
+Click the button below to start! 
+
+image::button-start-standard.png[link=standard-path.adoc]
+
+== Extended Paths
+
+The workshop also contains extended paths for Developers or Operations Engineers.
+The extended paths go into much greater detail regarding features and capabilities of Kubernetes specifically for those Teams. 
+We recommend at least 4 hours for each of the extended paths.
+
+Click on one of the two buttons below to start!
+
+:frame: none
+:grid: none
+:valign: top
+
+[align="center", cols="2*"]
 |=====
-|link:developer-path.adoc[For Developers or Development Teams]
-|link:operations-path.adoc[For Operations Engineers or Operations Teams]
+|image:button-start-developer.png[link=developer-path.adoc]
+|image:button-start-operations.png[link=operations-path.adoc]
 |=====
 
-For those looking for a more condensed introduction to Kubernetes on AWS, there is also a link:combined-path.adoc[Combined Version], which should take approximately 2 hours to complete.
-
 
 NOTE: You will incur charges as you go through these workshop guides as it will exceed the link:http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/free-tier-limits.html[limits of AWS free tier]. An estimate of charges (<$20/day) can be seen at this link:https://calculator.s3.amazonaws.com/index.html#r=FRA&s=EC2&key=calc-E6DBD6F1-C45D-4827-93F8-D9B18C5994B0[simple monthly calculator]