From f27c914f829d1250fae059842eef0eebca56363c Mon Sep 17 00:00:00 2001 From: Federico Hernandez Date: Thu, 9 Dec 2021 16:10:45 +0100 Subject: [PATCH 1/2] Document CoreDNS configuration settings Cluster spec settings to override the default resource request and limit values of CoreDNS . Currently not documented. Reference: - https://github.com/kubernetes/kops/blob/1c78abb288a06b5719e4750b63b7ef06c967de84/upup/models/cloudup/resources/addons/coredns.addons.k8s.io/k8s-1.12.yaml.template#L156-L161 - https://github.com/kubernetes/kops/blob/1c78abb288a06b5719e4750b63b7ef06c967de84/pkg/apis/kops/v1alpha2/cluster.go#L476-L515 --- docs/cluster_spec.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/cluster_spec.md b/docs/cluster_spec.md index 5f85a9b620..4052510c3d 100644 --- a/docs/cluster_spec.md +++ b/docs/cluster_spec.md @@ -830,6 +830,22 @@ 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 + +- memoryLimit +- cpuRequest +- memoryRequest + +This will override the default limit value for memory of 170Mi and default request values for memory and cpu of 70Mi and 100m. + +Example: +``` + kubeDNS: + memoryLimit: 2Gi + cpuRequest: 300m + memoryRequest: 700Mi +``` + ## kubeControllerManager This block contains configurations for the `controller-manager`. From 32ddea49c1773161fc747fb77ed9f64dfe06ea72 Mon Sep 17 00:00:00 2001 From: Federico Hernandez Date: Thu, 9 Dec 2021 22:08:03 +0100 Subject: [PATCH 2/2] 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