k3s/cluster/images/hyperkube
Jeff Grafton b4635a829a Update to use debian-iptables v10.2 and debian-hyperkube-base 0.10.2 2018-09-17 21:10:04 -07:00
..
BUILD Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
Dockerfile cluster/images/hyperkube: Fix typo in Dockerfile for aggregator symlink 2018-02-15 17:44:02 -05:00
Makefile Update to use debian-iptables v10.2 and debian-hyperkube-base 0.10.2 2018-09-17 21:10:04 -07:00
OWNERS Add Labels to various OWNERS files 2018-08-21 13:59:08 -04:00
README.md Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -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 staging-k8s.gcr.io

$ make push VERSION={target_version} ARCH=amd64
# ---> staging-k8s.gcr.io/hyperkube-amd64:VERSION
# ---> staging-k8s.gcr.io/hyperkube:VERSION (image with backwards-compatible naming)

$ make push VERSION={target_version} ARCH=arm
# ---> staging-k8s.gcr.io/hyperkube-arm:VERSION

$ make push VERSION={target_version} ARCH=arm64
# ---> staging-k8s.gcr.io/hyperkube-arm64:VERSION

$ make push VERSION={target_version} ARCH=ppc64le
# ---> staging-k8s.gcr.io/hyperkube-ppc64le:VERSION

$ make push VERSION={target_version} ARCH=s390x
# ---> staging-k8s.gcr.io/hyperkube-s390x:VERSION

If you don't want to push the images, run make or make build instead

Analytics