k3s/cluster/addons/dns-horizontal-autoscaler
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
..
MAINTAINERS.md Adds docs for dns-horizontal-autoscaler and kube-dns 2016-12-07 11:36:08 -08:00
OWNERS OWNERS: Update latest OWNERS files 2017-01-23 10:05:48 -08:00
README.md Adds kubernetes.io link for dns autoscaler addon 2016-12-20 10:43:24 -08:00
dns-horizontal-autoscaler.yaml Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00

README.md

DNS Horizontal Autoscaler

DNS Horizontal Autoscaler enables horizontal autoscaling feature for DNS service in Kubernetes clusters. This autoscaler runs as a Deployment. It collects cluster status from the APIServer, horizontally scales the number of DNS backends based on demand. Autoscaling parameters could be tuned by modifying the kube-dns-autoscaler ConfigMap in kube-system namespace.

Learn more about:

Analytics