2016-04-04 20:33:32 +00:00
|
|
|
### hyperkube
|
|
|
|
|
|
|
|
|
|
`hyperkube` is an all-in-one binary for the Kubernetes server components
|
2017-04-16 21:54:08 +00:00
|
|
|
`hyperkube` is built for multiple architectures and _the image is pushed automatically on every release._
|
2016-04-04 20:33:32 +00:00
|
|
|
|
|
|
|
|
#### How to release by hand
|
|
|
|
|
|
|
|
|
|
```console
|
2016-04-14 04:29:10 +00:00
|
|
|
# First, build the binaries
|
2016-12-14 00:03:06 +00:00
|
|
|
$ build/run.sh make cross
|
2016-04-04 20:33:32 +00:00
|
|
|
|
|
|
|
|
# Build for linux/amd64 (default)
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# export REGISTRY=$HOST/$ORG to switch from staging-k8s.gcr.io
|
2017-05-12 00:23:17 +00:00
|
|
|
|
2016-04-04 20:33:32 +00:00
|
|
|
$ make push VERSION={target_version} ARCH=amd64
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# ---> staging-k8s.gcr.io/hyperkube-amd64:VERSION
|
|
|
|
|
# ---> staging-k8s.gcr.io/hyperkube:VERSION (image with backwards-compatible naming)
|
2016-04-04 20:33:32 +00:00
|
|
|
|
|
|
|
|
$ make push VERSION={target_version} ARCH=arm
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# ---> staging-k8s.gcr.io/hyperkube-arm:VERSION
|
2016-04-14 04:29:10 +00:00
|
|
|
|
|
|
|
|
$ make push VERSION={target_version} ARCH=arm64
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# ---> staging-k8s.gcr.io/hyperkube-arm64:VERSION
|
2016-04-14 04:29:10 +00:00
|
|
|
|
|
|
|
|
$ make push VERSION={target_version} ARCH=ppc64le
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# ---> staging-k8s.gcr.io/hyperkube-ppc64le:VERSION
|
2016-11-18 13:52:21 +00:00
|
|
|
|
|
|
|
|
$ make push VERSION={target_version} ARCH=s390x
|
Switch to k8s.gcr.io vanity domain
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.
2018-01-17 19:36:53 +00:00
|
|
|
# ---> staging-k8s.gcr.io/hyperkube-s390x:VERSION
|
2016-04-04 20:33:32 +00:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
If you don't want to push the images, run `make` or `make build` instead
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[]()
|
