k3s/examples/cluster-dns
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
..
images Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
README.md add redirect notice in all readme files 2017-07-14 17:18:01 +02:00
dns-backend-rc.yaml Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
dns-backend-service.yaml update examples/cluster-dns to v1 2015-06-09 14:26:41 -07:00
dns-frontend-pod.yaml Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
namespace-dev.yaml update examples/cluster-dns to v1 2015-06-09 14:26:41 -07:00
namespace-prod.yaml update examples/cluster-dns to v1 2015-06-09 14:26:41 -07:00