2016-08-23 13:24:42 +00:00
|
|
|
## serve_hostname
|
2016-03-03 17:22:43 +00:00
|
|
|
|
2016-08-23 13:24:42 +00:00
|
|
|
This is a small util app to serve your hostname on TCP and/or UDP. Useful for testing.
|
|
|
|
|
|
|
|
|
|
The `serve_hostname` Makefile supports multiple architectures, which means it may cross-compile and build an docker image easily.
|
|
|
|
|
Arch-specific busybox images serve as base images.
|
|
|
|
|
|
|
|
|
|
If you are releasing a new version, please bump the `TAG` value in the `Makefile` before building the images.
|
|
|
|
|
|
|
|
|
|
## How to release:
|
|
|
|
|
|
|
|
|
|
```
|
2016-09-10 11:30:48 +00:00
|
|
|
# Build cross-platform binaries
|
|
|
|
|
$ make all-push
|
|
|
|
|
|
2016-08-23 13:24:42 +00:00
|
|
|
# Build for linux/amd64 (default)
|
|
|
|
|
$ make push 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/serve_hostname-amd64:TAG
|
2016-08-23 13:24:42 +00:00
|
|
|
|
|
|
|
|
$ make push 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/serve_hostname-arm:TAG
|
2016-08-23 13:24:42 +00:00
|
|
|
|
|
|
|
|
$ make push 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/serve_hostname-arm64:TAG
|
2016-08-23 13:24:42 +00:00
|
|
|
|
|
|
|
|
$ make push 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/serve_hostname-ppc64le:TAG
|
2016-11-18 13:52:21 +00:00
|
|
|
|
|
|
|
|
$ make push 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/serve_hostname-s390x:TAG
|
2016-08-23 13:24:42 +00:00
|
|
|
```
|
|
|
|
|
|
2016-09-10 11:30:48 +00:00
|
|
|
Of course, if you don't want to push the images, run `make all-container` or `make container ARCH={target_arch}` instead.
|
2016-03-03 17:22:43 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
[]()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[]()
|
