k3s/cluster/images/hyperkube
David McMahon d65005bdb2 Honor make variable OUT_DIR. 2018-01-03 17:46:03 -08:00
..
BUILD Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -08:00
Dockerfile Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -08:00
Makefile Honor make variable OUT_DIR. 2018-01-03 17:46:03 -08:00
README.md Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -08: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

Analytics