kube-dns autoscaler: set min replicas to 2

Issue https://github.com/kubernetes/kubernetes/issues/40063

Having a single pod would be a single point of failure.  Multiple pods
should be spread across AZs & nodes by k8s automatically.
This commit is contained in:
Justin Santa Barbara 2017-01-23 09:22:33 -05:00
parent 4d49abb272
commit 7899864409
4 changed files with 6 additions and 6 deletions

View File

@ -46,7 +46,7 @@ spec:
- --target=Deployment/kube-dns
# 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}}
- --default-params={"linear":{"coresPerReplica":256,"nodesPerReplica":16,"min":2}}
- --logtostderr=true
- --v=2

View File

@ -85,7 +85,7 @@ func (b *BootstrapChannelBuilder) buildManifest() (*channelsapi.Addons, map[stri
{
key := "kube-dns.addons.k8s.io"
version := "1.5.0"
version := "1.5.1"
location := key + "/v" + version + ".yaml"

View File

@ -9,11 +9,11 @@ spec:
selector:
k8s-addon: core.addons.k8s.io
version: 1.4.0
- manifest: kube-dns.addons.k8s.io/v1.5.0.yaml
- manifest: kube-dns.addons.k8s.io/v1.5.1.yaml
name: kube-dns.addons.k8s.io
selector:
k8s-addon: kube-dns.addons.k8s.io
version: 1.5.0
version: 1.5.1
- manifest: limit-range.addons.k8s.io/v1.5.0.yaml
name: limit-range.addons.k8s.io
selector:

View File

@ -9,11 +9,11 @@ spec:
selector:
k8s-addon: core.addons.k8s.io
version: 1.4.0
- manifest: kube-dns.addons.k8s.io/v1.5.0.yaml
- manifest: kube-dns.addons.k8s.io/v1.5.1.yaml
name: kube-dns.addons.k8s.io
selector:
k8s-addon: kube-dns.addons.k8s.io
version: 1.5.0
version: 1.5.1
- manifest: limit-range.addons.k8s.io/v1.5.0.yaml
name: limit-range.addons.k8s.io
selector: