Use cases

• Developer runs a local copy of Labs Workbench on their laptop or a VM (AWS, GCE, Azure, OpenStack etc).
  
  

Options:

• Kubernetes Hyperkube
• Minikube
• CoreOS single-node Vagrant (Hyperkube)
• CoreOS multi-node Vagrant
• VirtualBox
  
  

Minikube

Minikube runs Kubernetes in a single VM.

• Download binary
• minikube start creates a VM in VirtualBox (or other virtualization environment)
• Sets up kubeconfig and local environment to access VM via kubectl

MacOS

• Install VirtualBox
• Download binary
• minikube start
• git clone ndslabs-up.sh
• Don't need kube-up.sh, since we're running Minikube
• ndslabs-up.sh 
  • Local DNS via bind works!
  • IP detection, etcd, etc, won't work as-is

Windows 10

• Install VirtualBox (can also use Hyper-V, but not tested here)
  • Disable Hyper-V: Settings > Turn Windows Features on or off; uncheck Hyper-V
• Download minikube for Windows
• minikube.exe start
  • Will make changes to VirtualBox

Hyperkube

• Our current ndslabs-startup/kube-up relies on Hyperkube, which is basically Kubernetes in Docker. 
  • gcr.io/google_containers/hyperkube-amd64
• Hyperkube works fine on CoreOS boxes in OpenStack, but has proven problematic under Docker for Mac and Docker for Windows due to permissions problems.
• The CoreOS project provides a process for launching Kubernetes on CoreOS, using another hyperkube image
  • https://coreos.com/kubernetes/docs/latest/kubernetes-on-generic-platforms.html
  • Uses quay.io/coreos/hyperkube image

...