Review for Kubernetes

The fault handling and resource management has always been a big problem in large-scale cluster computing. although the problem has been solve by many other works like Mesos, Yarn, etc. , the project Kubernetes want to solve this problem at massive scale.

The key idea of Cabernets is to place applications into Docker containers on multiple host nodes. And the whole project is based on Google's Borg project. It has several key concepts.

1. Pods: it is the unit of scheduling in Kubernetes. It has the resources that enable one or several containers to run.
2. Services: it enable naming and load balancing on Kubernetes.
3. Lables: It is arbitrary key/value pairs that user attached on Pods. Compared with Borg, it enables more flexible collections by organizing Pods.

The work flow of Cabernets is illustrated as the figure above. The Kubernetes consists of Kubecfg, Master API Server, Kubelet, Minion(Host) and Proxy.

The master defines Master/API sever's main statements, including Pod Registry, controller Registry, Service Registry, endpoint registry, minion registry, binding registry, etc. It is the center for client (Kubecfg) calling Kubernetes's API, container control. Master has API Server, Scheduler and Registry components.

Kubelet is the connecting point of Minion and Master API server.

Proxy is designed for using Kubernets's containers from outside internet.

The difference of Kubernetes from other previous works is main in 3 aspects.

1. Kubernetes enables lightwight, simple access.

2. it can build multiple-cloud.

3. it is highly extensible.

For the project's influence, I am quite sure container is a trend for cloud computing, since it provides a simple interface for programmer to use the clusters.