Files
kubernetes/test/images/serve-hostname/README.md
Tim Hockin 3586986416 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-02-07 21:14:19 -08:00

1.2 KiB

serve_hostname

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:

# Build cross-platform binaries
$ make all-push

# Build for linux/amd64 (default)
$ make push ARCH=amd64
# ---> staging-k8s.gcr.io/serve_hostname-amd64:TAG

$ make push ARCH=arm
# ---> staging-k8s.gcr.io/serve_hostname-arm:TAG

$ make push ARCH=arm64
# ---> staging-k8s.gcr.io/serve_hostname-arm64:TAG

$ make push ARCH=ppc64le
# ---> staging-k8s.gcr.io/serve_hostname-ppc64le:TAG

$ make push ARCH=s390x
# ---> staging-k8s.gcr.io/serve_hostname-s390x:TAG

Of course, if you don't want to push the images, run make all-container or make container ARCH={target_arch} instead.

Analytics

Analytics