From 32ddea49c1773161fc747fb77ed9f64dfe06ea72 Mon Sep 17 00:00:00 2001 From: Federico Hernandez Date: Thu, 9 Dec 2021 22:08:03 +0100 Subject: [PATCH] Update docs/cluster_spec.md Co-authored-by: Ole Markus With --- docs/cluster_spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cluster_spec.md b/docs/cluster_spec.md index 4052510c3d..a28cf72fc1 100644 --- a/docs/cluster_spec.md +++ b/docs/cluster_spec.md @@ -830,7 +830,7 @@ spec: **Note:** If you are upgrading to CoreDNS, kube-dns will be left in place and must be removed manually (you can scale the kube-dns and kube-dns-autoscaler deployments in the `kube-system` namespace to 0 as a starting point). The `kube-dns` Service itself should be left in place, as this retains the ClusterIP and eliminates the possibility of DNS outages in your cluster. If you would like to continue autoscaling, update the `kube-dns-autoscaler` Deployment container command for `--target=Deployment/kube-dns` to be `--target=Deployment/coredns`. -For larger clusters you may need to set custom resource requests and limits. For the CoreDNS provicer you can set +For larger clusters you may need to set custom resource requests and limits. For the CoreDNS provider you can set - memoryLimit - cpuRequest