k8s0: Kubernetes Ground Zero

It's a minimal kubernetes installation on a fixed configuration.

But WHY ? Many people told me there's alreday MiniKube. Unlike MiniKube, which is a layer of golang code wrapped around the real hyperkube, k8s0 uses the exact hyperkube image. It's more like a minimal version of Kargo, but with the capability to run on Travis.

Another advantage of k8s0 is we have a step of pulling all necessary images before actual installation. This is very helpful if you are not able to access the internet during the installation, for example, behind the company's firewall, or in some "evil countries" where all google sites are banned. The solution is run the pull image step on a computer with internet connection. After you run images.yml, all images will be copied into images folder. Then you can copy these tar files to the isolated env. and run the rest installation.

So the user can try this on local host or VM, or use it on Travis for kubernetes DevOps. Developers can verify their service deployment before going to the real production env. And the ansible script make it easy to tweak the installation steps for more usages. On the other hand, if you want to change anything in MiniKube, you have to write golang code and compile it.

Addtionally, people use MiniKube mainly for education purposes, but the one giant piece golang code of MiniKube makes it difficult to understand how k8s is installed and how each component interacts. Within k8s0, each installation step is nicely organized as role of ansible script. It is very straight-forward to follow.

One more thing, all components are installed as containers including etcd, kubelet, calico, ...

Current status: installed etcd, kubelet, api server, controller, scheduler, proxy, and calico as network plugin.

Impediments:

Prerequisites

For now, only support ubuntu >=14.04 with docker and ansible installed.

Usage

Deploy using Vagrant

Use vagrant vagrant up in the source root folder. P.S. for Chinese users, you have to use VAGRANT_VAGRANTFILE=Vagrantfile.cn vagrant up

There's also a sample vagrant file for multiple nodes, one master and one worker node. Its name is Vagrantfile.multi.

Deploy on Travis

Check .travis.yml for more details.

Deploy on localhost

# P.S., deploy to localhost has some issue on calico, pls use single host if you want a functional network.
# pull images and put into ./images folder
ansible-playbook -i inventory/local images.yml # for China, add: --extra-vars "china=True"

# start kubernetes on localhost
ansible-playbook -i inventory/local site.yml

Deploy to a remote host

# change ip to the remote host or your local actual ip.
https://github.com/reachlin/k8s0/blob/master/inventory/single/inventory

# pull images and put into ./images folder
ansible-playbook -i inventory/single images.yml # for China, add: --extra-vars "china=True"

# start kubernetes on localhost
ansible-playbook -i inventory/single site.yml

Deploy to multi remote hosts

# change ips
https://github.com/reachlin/k8s0/blob/master/inventory/multi/inventory

# pull images and put into ./images folder
ansible-playbook -i inventory/multi images.yml # for China, add: --extra-vars "china=True"

# start kubernetes on localhost
ansible-playbook -i inventory/multi site.yml

If you want to add a new worker node, please checkout the worker.yml. It's also used in Vagrantfile.multi.

P.S, to use kubectl on a worker node, export env for the configure file: export KUBECONFIG=/etc/kubernetes/kubelet-config.yml.

Features

Minimal kubernetes on travis for DevOps.
Include a local copy of all images, so kubernetes can be deployed without an internet connection.
All k8s components running as containers.
Support multiple nodes!

Dev. Notes

Basic steps

etcd -> kubelet -> api server as static pod -> other k8s pods -> calico

Treak the versions

If you want to change the version of various container images of k8s, pls refer to registry/defaults/main.yml.

References

Create certificates

openssl genrsa -out ca.key 2048
openssl req -x509 -new -nodes -key ca.key -subj "/CN=k8s0-ca" -days 99999 -out ca.crt -sha256
openssl x509 -in ca.crt -text -noout
openssl genrsa -out kubelet.key 2048
openssl req -new -key kubelet.key -subj "/CN=kubelet" -out kubelet.csr
openssl x509 -req -in kubelet.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out kubelet.crt -days 99999 -sha256
openssl x509 -in kubelet.crt -text -noout
openssl genrsa -out server.key 2048
openssl req -new -key server.key -subj "/CN=apiserver" -out server.csr
openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 99999 -sha256 -extensions req_ext -extfile openssl.conf
openssl x509 -in server.crt -text -noout

Useful commands

# clean all
docker ps -a --format "{{.ID}}"|xargs -L1 docker rm -f

last updated 02-01-2018, this is the version for hyperkube 1.8.4