mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue Moves dns-horizontal-autoscaler to a separate service account Similar to #38816. As one of the cluster add-ons, dns-horizontal-autoscaler is now using the default service account in kube-system namespace, which is introduced by https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/e2e-rbac-bindings/random-addon-grabbag.yaml for the ease of transition. This default service account will be removed in the future. This PR subdivides dns-horizontal-autoscaler to a separate service account and setup the necessary permissions. @bowei **Release note**: ```release-note NONE ``` |
||
---|---|---|
.. | ||
MAINTAINERS.md | ||
OWNERS | ||
README.md | ||
dns-horizontal-autoscaler-rbac.yaml | ||
dns-horizontal-autoscaler.yaml |
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:
- Usage: http://kubernetes.io/docs/tasks/administer-cluster/dns-horizontal-autoscaling/
- Implementation: https://github.com/kubernetes-incubator/cluster-proportional-autoscaler/