gcloud config set compute/zone us-east1-d
gcloud container clusters create kuar-cluster
gcloud container clusters delete kuar-cluster
gcloud auth application-default login

Kubernetest Proxy
-routes network traffic to load-balanced services in cluster

Kubernetes DNS
-naming and discovery within cluster

UI
-Everything is a REST API; command line client, scripts, and UI all do the same thing

Pods
-container(s) that share an IP and filesystem.  Allows you to group multiple containers but allocate CPU/memory differently

Liveness/Readiness
-Is it alive?  Should it receive traffic?

Labels
- ways to select different containers (we usually use DNS/IP to do this now)
Annotations:
- same thing as a label, only descriptions rather than selector

Service:
This is a way to interact with things outside of your pod.  Usually mounted on a Cluster IP which is basically a VIP.

Service Discovery
-Where is a database or web-server?  Again, usually solved with DNS/IP now in a static fashion.  Not reliable when IP is abstracted away
-NodePort: exposes a service so that if you can reach any node on it's external IP, you can hit the service
-Endpoints: individual pods that listen to a Service

ReplicaSet
- ReplicaSets are the best way to handle what *sets* of pods should do.  They decouple what a pod is from how it should behave in terms of scaling

DaemonSet
- This ensures at least one pod will live on every node.  Useful for monitoring and logging for example.

Jobs
-Pod that runs until succesful termination.  Think Lambda.

1.) Kubernetes is a Google product.  Google has been running containers in production since the mid 2000's.  The first production iteration was called Borg, the second was called Omega.  Kubernetes (Greek for helmsman/pilot) is the third iteration.  Started life as Project Seven to make a "friendlier borg".  7 spokes in the wheel is a nod to that codename.  Kubernetes also does some word association with Docker which is famous for the whale like Linux is famous for the penguin. (pods).
2.) Kubernetes is to Docker what VSphere is to ESXi guests.  It's orchestration and management, but it doesn't get into the business of redefining a container or container format.  It's actually a little closer to openstack in that you could bend it to use non-Docker containers, but there's seldom a great reason to.  It takes the pieces that Docker does well of definiing what a container is and how to build one, and adds orchestration to the whole thing to manage things like scheduling.
3.) What is a container?  A container is just a filesystem that gets run with some degree of process isolation.  It shares a common kernel, but beyond that can be isolated in process namespace, shared filesystems, network.  You can essentially run it as a small VM if you like.  Because the kernel is already running, it's very quick to start, and can be extremely tiny in size (Alpine Linux is only 5MB as a base image).
4.) So what does kubernetes do