52baf68d50
Signed-off-by: Michał Żyłowski <michal.zylowski@intel.com> |
||
---|---|---|
.. | ||
cni-conf | ||
static-pods | ||
copy-addons.sh | ||
Dockerfile | ||
kube-proxy-ds.yaml | ||
Makefile | ||
README.md | ||
setup-files.sh |
hyperkube
hyperkube
is an all-in-one binary for the Kubernetes server components
Also, it's very easy to run this hyperkube
setup dockerized.
See https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md for up-to-date commands.
hyperkube
is built for multiple architectures and pushed automatically on every release.
How to release by hand
# First, build the binaries
$ build/run.sh make cross
# Build for linux/amd64 (default)
$ make push VERSION={target_version} ARCH=amd64
# ---> gcr.io/google_containers/hyperkube-amd64:VERSION
# ---> gcr.io/google_containers/hyperkube:VERSION (image with backwards-compatible naming)
$ make push VERSION={target_version} ARCH=arm
# ---> gcr.io/google_containers/hyperkube-arm:VERSION
$ make push VERSION={target_version} ARCH=arm64
# ---> gcr.io/google_containers/hyperkube-arm64:VERSION
$ make push VERSION={target_version} ARCH=ppc64le
# ---> gcr.io/google_containers/hyperkube-ppc64le:VERSION
$ make push VERSION={target_version} ARCH=s390x
# ---> gcr.io/google_containers/hyperkube-s390x:VERSION
If you don't want to push the images, run make
or make build
instead