3586986416
This is the 2nd attempt. The previous was reverted while we figured out the regional mirrors (oops). New plan: k8s.gcr.io is a read-only facade that auto-detects your source region (us, eu, or asia for now) and pulls from the closest. To publish an image, push k8s-staging.gcr.io and it will be synced to the regionals automatically (similar to today). For now the staging is an alias to gcr.io/google_containers (the legacy URL). When we move off of google-owned projects (working on it), then we just do a one-time sync, and change the google-internal config, and nobody outside should notice. We can, in parallel, change the auto-sync into a manual sync - send a PR to "promote" something from staging, and a bot activates it. Nice and visible, easy to keep track of.
34 lines
907 B
Markdown
34 lines
907 B
Markdown
### debian-hyperkube-base
|
|
|
|
Serves as the base image for `k8s.gcr.io/hyperkube-${ARCH}`
|
|
images.
|
|
|
|
This image is compiled for multiple architectures.
|
|
|
|
#### How to release
|
|
|
|
If you're editing the Dockerfile or some other thing, please bump the `TAG` in the Makefile.
|
|
|
|
```console
|
|
# Build for linux/amd64 (default)
|
|
$ make push ARCH=amd64
|
|
# ---> staging-k8s.gcr.io/debian-hyperkube-base-amd64:TAG
|
|
|
|
$ make push ARCH=arm
|
|
# ---> staging-k8s.gcr.io/debian-hyperkube-base-arm:TAG
|
|
|
|
$ make push ARCH=arm64
|
|
# ---> staging-k8s.gcr.io/debian-hyperkube-base-arm64:TAG
|
|
|
|
$ make push ARCH=ppc64le
|
|
# ---> staging-k8s.gcr.io/debian-hyperkube-base-ppc64le:TAG
|
|
|
|
$ make push ARCH=s390x
|
|
# ---> staging-k8s.gcr.io/debian-hyperkube-base-s390x:TAG
|
|
```
|
|
|
|
If you don't want to push the images, run `make build` instead
|
|
|
|
|
|
[]()
|