Docker Cookbook

5.10 Compiling Kubernetes to Create Your Own Release | 155

---

├── integration
├── kube-apiserver
├── kube-controller-manager
├── kubectl
├── kubelet
├── kube-proxy
├── kubernetes
├── kube-scheduler
└── web-server
Discussion
Similarly, you can also build the complete set of release artifacts. They will be deliv‐
ered as tarballs with 
kubernetes.tar.gz
containing all binaries, examples, add-ons, and
deployment scripts. Creating the release will take more time than simply building the
binaries; all end-to-end tests will run. To build a full release, do the following and
check that the 
/_output/release-tars/
directory contains all the tarballs:
$ ./build/release.sh
$ tree _output/release-tars/
_output/release-tars/
├── kubernetes-client-darwin-386.tar.gz
├── kubernetes-client-darwin-amd64.tar.gz
├── kubernetes-client-linux-386.tar.gz
├── kubernetes-client-linux-amd64.tar
├── kubernetes-client-linux-arm.tar.gz
├── kubernetes-client-windows-amd64.tar.gz
├── kubernetes-salt.tar.gz
├── kubernetes-server-linux-amd64.tar.gz
├── kubernetes.tar.gz
└── kubernetes-test.tar.gz
In addition to the tarballs, the release process will create three Docker images for the
three main components of a Kubernetes cluster: the API server, the controller, and
the scheduler:
# docker images
REPOSITORY ...
gcr.io/google_containers/kube-controller-manager ...
gcr.io/google_containers/kube-scheduler ...
gcr.io/google_containers/kube-apiserver ...
156 | Chapter 5: Kubernetes

---

The release contains a Dockerfile that builds an image containing
the 
hyperkube
binary. This binary can be used to start all the com‐
ponents of a Kubernetes cluster. This is what was used in 
Recipe 5.9
to run Kubernetes in a single node using Docker containers. You
can use this Dockerfile to build your own Hyperkube image and
edit the configuration file 
master.json
to your liking:
$ tree kubernetes/cluster/images/hyperkube/
kubernetes/cluster/images/hyperkube/
├── Dockerfile
├── Makefile
├── master.json
└── master-multi.json