github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/images/hyperkube
History
Davanum Srinivas f16b00b321 update build/root/WORKSPACE and cluster/images/hyperkube/Makefile for the new tag 2017-11-29 14:15:58 -05:00
..
BUILD Remove all traces of federation 2017-10-26 13:37:37 -07:00
Dockerfile Remove all traces of federation 2017-10-26 13:37:37 -07:00
Makefile update build/root/WORKSPACE and cluster/images/hyperkube/Makefile for the new tag 2017-11-29 14:15:58 -05: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

Analytics