Move kops section to Appendix

Author: buzzsurfr

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

@@ -69,6 +69,7 @@ Once your Cloud9 is ready, download the build script and install in your IDE. Th
 - kubectl _(the Kubernetes CLI, which we'll cover in great detail later in the workshop)_
 - heptio/authenticator _(for authentication to the EKS cluster)_
 - updates/configures the AWS CLI and stores necessary environment variables in bash_profile
+- kops _(Kubernetes Operations, which we'll also cover in detail later)_
 - creates an SSH key
 - clone the workshop repository into Cloud9
 
@@ -106,7 +107,7 @@ You are now ready to continue on with the workshop!
 |link:../../operations-path.adoc[Go to Operations Index]
 |=====
 
-The next step is link:../102-your-first-cluster[to create a Kubernetes cluster using EKS].
+The next step is link:../102-your-first-cluster[to create a Kubernetes cluster].
 
 
 == Workshop Cleanup
@@ -116,6 +117,8 @@ Once you have finished with the workshop, please don't forget to spin down your
 
 Ensure that you have deleted all services, etc from the `default` namespace before proceeding.
 
+=== Using EKS
+
 ==== Delete EKS worker nodeds
 
 Go to CloudFormation console, right click template with name 'k8s-workshop-worker-nodes' and select 'Delete Stack'
@@ -132,7 +135,21 @@ Delete EKS cluster
 
 Wait until all resources are deleted by kops
 
-==== Delete Cloud9 Envionment
+=== Using kops
+
+==== Delete Kubernetes cluster resources
+
+In your Cloud9 IDE, check if there are any running kubernetes cluster
+
+   $ kops get cluster
+
+Delete kubernetes cluster
+
+   $ kops delete cluster example.cluster.k8s.local --yes
+
+Wait until all resources are deleted by kops
+
+=== Delete Cloud9 Envionment
 
 Go to CloudFormation console, right click template with name 'k8s-workshop' and select 'Delete Stack'
 

01-path-basics/101-start-here/scripts/lab-ide-build.sh

@@ -25,6 +25,11 @@ chmod +x kubectl && sudo mv kubectl /usr/local/bin/
 curl -o heptio-authenticator-aws https://amazon-eks.s3-us-west-2.amazonaws.com/1.10.3/2018-06-05/bin/linux/amd64/heptio-authenticator-aws
 chmod +x ./heptio-authenticator-aws && sudo mv heptio-authenticator-aws /usr/local/bin/
 
+# Install kops
+curl -LO https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64
+chmod +x kops-linux-amd64
+sudo mv kops-linux-amd64 /usr/local/bin/kops
+
 # Configure AWS CLI
 availability_zone=$(curl http://169.254.169.254/latest/meta-data/placement/availability-zone)
 export AWS_DEFAULT_REGION=${availability_zone%?}
@@ -47,7 +52,6 @@ export EKS_SECURITY_GROUPS=$(aws cloudformation describe-stacks --stack-name $AW
 export EKS_SERVICE_ROLE=$(aws cloudformation describe-stacks --stack-name $AWS_MASTER_STACK | jq -r '.Stacks[0].Outputs[]|select(.OutputKey=="EksServiceRoleArn")|.OutputValue')
 
 # Persist lab variables
-echo "export PATH=$HOME/go/bin:$PATH" >> ~/.bashrc
 echo "AWS_AVAILABILITY_ZONES=$AWS_AVAILABILITY_ZONES" >> ~/.bash_profile
 echo "KOPS_STATE_STORE=$KOPS_STATE_STORE" >> ~/.bash_profile
 echo "export AWS_AVAILABILITY_ZONES KOPS_STATE_STORE" >> ~/.bash_profile

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

@@ -140,3 +140,120 @@ The next step is link:../103-kubernetes-concepts[to learn about basic Kubernetes
 
 The sections below provide information on other capabilities of Kubernetes clusters.
 You are welcome to read and refer to them should you need to use those capabilities.
+
+== Alternative: Create a Kubernetes Cluster with kops
+
+This section will walk you through how to install a Kubernetes cluster on AWS using kops.
+
+https://github.com/kubernetes/kops[kops, window="_blank"], short for Kubernetes Operations, is a set of tools for installing, operating, and deleting Kubernetes clusters. kops can also perform rolling upgrades from older versions of Kubernetes to newer ones, and manage the cluster add-ons.
+
+kops can be used to create a highly available cluster, with multiple master and worker nodes spread across multiple availability zones.
+The master and worker nodes within the cluster can use either DNS or the https://github.com/weaveworks/mesh[Weave Mesh, window="_blank"] *gossip* protocol for name resolution.  For this workshop, we will use the gossip protocol.  A gossip-based cluster is easier and quicker to setup, and does not require a domain, subdomain, or Route53 hosted zone to be registered. Instructions for creating a DNS-based cluster are provided as an appendix at the bottom of this page.
+
+To create a cluster using the gossip protocol, simply use a cluster name with a suffix of `.k8s.local`. In the following steps, we will use `example.cluster.k8s.local` as a sample gossip cluster name. You may choose a different name as long as it ends with `.k8s.local`.
+
+We show two examples of creating gossip-based clusters below. You can choose whether to create a single-master or multi-master cluster. Most workshop exercises will work on both types of cluster, however some modules require using a multi-master cluster _(to demonstrate rolling updates, for instance)._ If you aren't sure, please create a xref:multi-master[multi-master cluster].
+
+=== Single-Master Cluster
+
+By default, the `kops create cluster` command creates a single master node and two worker nodes in the specified zones.
+
+Create a Kubernetes cluster using the following command. Run it in the "bash" terminal tab at the bottom of the Cloud9 IDE. This will create a cluster with a single master, multi-node and multi-az configuration:
+
+    $ kops create cluster \
+      --name example.cluster.k8s.local \
+      --zones $AWS_AVAILABILITY_ZONES \
+      --yes
+
+The `AWS_AVAILABILITY_ZONES` environment variable should have been set during the link:../101-start-here[Cloud9 Environment Setup].
+
+The `create cluster` command only creates and stores the cluster config in the S3 bucket. Adding the `--yes` flag ensures that the cluster is immediately created as well.
+
+Once the `kops create cluster` command is issued, it provisions the EC2 instances, sets up Auto Scaling Groups, IAM users, Security Groups, installs Kubernetes on each node, then configures the master and worker nodes. This process can take some time based upon the number of master and worker nodes.
+
+Note: If your 'create cluster' fails with an error like:
+```
+error reading s3://example-kops-state-store/example.cluster.k8s.local/config: Unable to list AWS regions: NoCredentialProviders: no valid providers in chain
+caused by: EnvAccessKeyNotFound: failed to find credentials in the environment."
+```
+Please confirm the following environment variables are set before executing the 'create cluster' command:
+```
+echo $AWS_DEFAULT_PROFILE
+echo $KOPS_STATE_STORE
+echo $AWS_SDK_LOAD_CONFIG
+```
+If any of those environment variables are blank, please re-run the "Build Script" section of the link:../101-start-here[Cloud9 Environment Setup].
+
+Wait for 5-8 minutes and then the cluster can be validated as shown:
+
+```
+$ kops validate cluster
+Using cluster from kubectl context: example.cluster.k8s.local
+
+Validating cluster example.cluster.k8s.local
+
+INSTANCE GROUPS
+NAME      ROLE  MACHINETYPE MIN MAX SUBNETS
+master-eu-central-1a Master  m3.medium 1 1 eu-central-1a
+nodes     Node  t2.medium 2 2 eu-central-1a,eu-central-1b
+
+NODE STATUS
+NAME        ROLE  READY
+ip-172-20-57-94.ec2.internal  master  True
+ip-172-20-63-55.ec2.internal  node  True
+ip-172-20-75-78.ec2.internal  node  True
+
+Your cluster example.cluster.k8s.local is ready
+```
+
+anchor:multi-master[]
+
+=== Multi-Master Cluster
+
+The command below creates a cluster in a multi-master, multi-node, and multi-az configuration.
+Run it in the "bash" terminal tab at the bottom of the Cloud9 IDE.
+We can create and build the cluster in one step by passing the `--yes` flag.
+
+    $ kops create cluster \
+      --name example.cluster.k8s.local \
+      --master-count 3 \
+      --node-count 5 \
+      --zones $AWS_AVAILABILITY_ZONES \
+      --yes
+
+A multi-master cluster can be created by using the `--master-count` option and specifying the number of master nodes. An odd value is recommended. By default, the master nodes are spread across the AZs specified using the `--zones` option. Alternatively, you can use the `--master-zones` option to explicitly specify the zones for the master nodes.
+
+The `--zones` option is also used to distribute the worker nodes. The number of workers is specified using the `--node-count` option.
+
+It will take 5-8 minutes for the cluster to be created. Validate the cluster:
+
+```
+$ kops validate cluster
+Using cluster from kubectl context: example.cluster.k8s.local
+
+Validating cluster example.cluster.k8s.local
+
+INSTANCE GROUPS
+NAME      ROLE  MACHINETYPE MIN MAX SUBNETS
+master-eu-central-1a Master  m3.medium 1 1 eu-central-1a
+master-eu-central-1b Master  m3.medium 1 1 eu-central-1b
+master-eu-central-1c Master  c4.large  1 1 eu-central-1c
+nodes     Node  t2.medium 5 5 eu-central-1a,eu-central-1b,eu-central-1c
+
+NODE STATUS
+NAME        ROLE  READY
+ip-172-20-101-97.ec2.internal node  True
+ip-172-20-119-53.ec2.internal node  True
+ip-172-20-124-138.ec2.internal  master  True
+ip-172-20-35-15.ec2.internal  master  True
+ip-172-20-63-104.ec2.internal node  True
+ip-172-20-69-241.ec2.internal node  True
+ip-172-20-84-65.ec2.internal  node  True
+ip-172-20-93-167.ec2.internal master  True
+
+Your cluster example.cluster.k8s.local is ready
+```
+
+Note that all masters are spread across different AZs.
+
+Your output may differ slightly from the one shown here based up on the type of cluster you created.

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

@@ -16,6 +16,9 @@ Kubernetes as a platform has a number of abstractions that map to API objects. T
 
 This chapter uses an EKS cluster with worker nodes as described link:../102-your-first-cluster[here].
 
+[NOTE]
+This lab and future labs can be completed using the EKS cluster or the multi-master kops cluster. Some of the outputs may vary slightly if using the kops cluster.
+
 All configuration files for this chapter are in the `01-path-basics/103-kubernetes-concepts/templates` directory.
 Please be sure to `cd` into that directory before running the commands below.