Docker Cookbook

See Also
• Building Kubernetes 
README
• Development environment using 
godep
5.11 Starting Kubernetes Components with the
hyperkube Binary
Problem
A Kubernetes cluster is made of a master node and several worker nodes. Each runs
several Kubernetes binaries. To ease deployment, you would like to use a single
binary, passing the type of component you want to start as an option to this binary.
Solution
Use 
hyperkube
.
As suggested in a tip at the end of 
Recipe 5.10
, a release contains all Kubernetes com‐
ponent binaries: the API server, the controller manager, the scheduler, the service
proxy, and the kubelet. The last two run on each worker node, while the first three
make up the Kubernetes master together with 
etcd
. 
hyperkube
is a single binary that
allows you to start all these components.
Assuming you created your own release as shown in 
Recipe 5.10
, you will find 
hyper‐
kube
in the 
_output/
directory:
# tree ~/kubernetes/_output/release-tars/kubernetes/server/kubernetes/server/bin
/root/kubernetes/_output/release-tars/kubernetes/server/kubernetes/server/bin
├── hyperkube
├── kube-apiserver
├── kube-apiserver.docker_tag
5.11 Starting Kubernetes Components with the hyperkube Binary | 157

---

├── kube-apiserver.tar
├── kube-controller-manager
├── kube-controller-manager.docker_tag
├── kube-controller-manager.tar
├── kubectl
├── kubelet
├── kube-proxy
├── kubernetes
├── kube-scheduler
├── kube-scheduler.docker_tag
└── kube-scheduler.tar
To use 
hyperkube
, you need to specify which component you want to start (i.e., 
api
server
, 
controller-manager
, 
scheduler
, 
kubelet
, or 
proxy
). Once you specify a
component, you can pass all the options that you choose. For example, to start the
API server, check the 
hyperkube
usage:
$ ./hyperkube apiserver -h
The main API entrypoint and interface to the storage system. The API server is
also the focal point for all authorization decisions.
Usage:
apiserver [flags]
Available Flags:
--address=127.0.0.1: DEPRECATED: see --insecure-bind-address instead
--admission-control="AlwaysAdmit": Ordered list of plug-ins to do ...
--admission-control-config-file="": File with admission control ...
--allow-privileged=false: If true, allow privileged containers.