kubernetes

History

Brandon Philips b9a96272f7 images: hyperkube: README: add a note about REGISTRY variable The REGISTRY variable is pretty helpful for people who are hacking on hyperkube. Document it here instead of just in the Makefile.		2017-05-11 17:24:23 -07:00
..
Dockerfile	Remove the old docker-multinode files that were built into the hyperkube image	2017-04-17 00:54:08 +03:00
Makefile	Fixing build break for federation	2017-04-20 22:29:53 -07:00
README.md	images: hyperkube: README: add a note about REGISTRY variable	2017-05-11 17:24:23 -07:00

README.md

hyperkube

hyperkube is an all-in-one binary for the Kubernetes server components hyperkube is built for multiple architectures and the image is pushed automatically on every release.

How to release by hand

# First, build the binaries
$ build/run.sh make cross

# Build for linux/amd64 (default)
# export REGISTRY=$HOST/$ORG to switch from gcr.io/google_containers

$ 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