Tim Bannister
7289483c7d
* Mark code blocks for syntax highlighting * Use glossary tooltips where appropriate * Reword DNS horizontal autoscaling task - Mention that addons manager is deprecated - Use unordered list for “What's next” * Note AMD64 instruction set assumption * Update to more recent cluster-proportional-autoscaler Based on sample configuration in https://raw.githubusercontent.com/kubernetes/kubernetes/beba9921aa1a73431bf322ffa17df6b2aa314b0c/cluster/addons/dns-horizontal-autoscaler/dns-horizontal-autoscaler.yaml
34 lines
943 B
YAML
34 lines
943 B
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: dns-autoscaler
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: dns-autoscaler
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
k8s-app: dns-autoscaler
|
|
template:
|
|
metadata:
|
|
labels:
|
|
k8s-app: dns-autoscaler
|
|
spec:
|
|
containers:
|
|
- name: autoscaler
|
|
image: k8s.gcr.io/cluster-proportional-autoscaler-amd64:1.6.0
|
|
resources:
|
|
requests:
|
|
cpu: 20m
|
|
memory: 10Mi
|
|
command:
|
|
- /cluster-proportional-autoscaler
|
|
- --namespace=kube-system
|
|
- --configmap=dns-autoscaler
|
|
- --target=<SCALE_TARGET>
|
|
# When cluster is using large nodes(with more cores), "coresPerReplica" should dominate.
|
|
# If using small nodes, "nodesPerReplica" should dominate.
|
|
- --default-params={"linear":{"coresPerReplica":256,"nodesPerReplica":16,"min":1}}
|
|
- --logtostderr=true
|
|
- --v=2
|