A Kubernetes multi-node cluster for developer of Kubernetes or extend Kubernetes. Based on kubeadm and Docker in Docker.

Docker 1.12+ is recommended. If you're not using one of the preconfigured scripts (see below) and not building from source, it's better to have kubectl executable in your path matching the version of k8s binaries you're using (i.e. for example better don't use kubectl 1.9.x with hyperkube 1.8.x).

kubernetes-cluster-over-docker supports k8s versions 1.8.x, 1.9.x .

Run kubernetes-cluster-over-docker on Docker with btrfs storage driver is not supported.

By default kubernetes-cluster-over-docker uses dockerized builds, so no Go installation is necessary even if you're building Kubernetes from source. If you want you can overridde this behavior by setting KUBEADM_DIND_LOCAL to a non-empty value in config.sh.

Ensure to have md5sha1sum installed. If not existing can be installed via brew install md5sha1sum.

When building Kubernetes from source on Mac OS X, it should be possible to build kubectl locally, i.e. make WHAT=cmd/kubectl must work.

kubernetes-cluster-over-docker currently provides preconfigured scripts for Kubernetes 1.8, 1.9. This may be convenient for use with projects that extend or use Kubernetes. For example, you can start Kubernetes 1.9 like this:

$ wget https://raw.githubusercontent.com/richardsonlima/kubernetes-docker-in-docker-cluster/master/kubernetes-docker-in-docker-cluster-v1.9.sh $ chmod +x kubernetes-docker-in-docker-cluster-v1.9.sh $ # start the cluster $ ./kubernetes-docker-in-docker-cluster-v1.9.sh up $ # also you can start the cluster with 3 nodes $ NUM_NODES=3 ./kubernetes-docker-in-docker-cluster-v1.9.sh up $ mkdir -p ~/.kube && \ sudo docker cp `sudo docker ps -a |grep kube-master \ |awk '{print $1}'`:/etc/kubernetes/admin.conf ~/.kube/config && \  sudo chown -R ${USER} ~/.kube # Downloading kubectl (1.9.9 - for linux)  $ curl -O https://storage.googleapis.com/kubernetes-release/release/v1.9.9/bin/linux/amd64/kubectl $ mv kubectl /usr/local/bin/ $ kubectl --kubeconfig ~/.kube/config get pods --all-namespaces # Creating a namespace $ kubectl --kubeconfig ~/.kube/config create namespace test-docker-in-docker $ kubectl --kubeconfig ~/.kube/config get nodes NAME STATUS ROLES AGE VERSION kube-master Ready master 57m v1.9.9 kube-node-1 Ready <none> 56m v1.9.9 kube-node-2 Ready <none> 56m v1.9.9 kube-node-3 Ready <none> 56m v1.9.9 $ # k8s dashboard available at http://localhost:8080/api/v1/namespaces/kube-system/services/kubernetes-dashboard:/proxy $ # restart the cluster, this should happen much quicker than initial startup $ ./kubernetes-docker-in-docker-cluster-v1.9.sh up $ # stop the cluster $ ./kubernetes-docker-in-docker-cluster-v1.9.sh down $ # remove containers and volumes $ ./kubernetes-docker-in-docker-cluster-v1.9.sh clean

Terminal session test::

Replace 1.8 with 1.9 or 1.10 to use other Kubernetes versions. Important note: you need to do ./kubernetes-docker-in-docker-cluster-....sh clean when you switch between Kubernetes versions (but no need to do this between rebuilds if you use BUILD_HYPERKUBE=y like described below).