DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ingress-nginx-helm/vendor/k8s.io/kubernetes/cluster/images/hyperkube
History
Manuel de Brito Fontes bf5616c65b Replace godep with dep
2017-10-06 17:26:14 -03:00
..
Dockerfile Replace godep with dep 2017-10-06 17:26:14 -03:00
Makefile Replace godep with dep 2017-10-06 17:26:14 -03:00
README.md Replace godep with dep 2017-10-06 17:26:14 -03: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