mirror of https://github.com/kubernetes/kops.git
Update docs/cluster_spec.md
Co-authored-by: Ole Markus With <olemarkus@gmail.com>
This commit is contained in:
parent
f27c914f82
commit
32ddea49c1
|
@ -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`.
|
**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
|
- memoryLimit
|
||||||
- cpuRequest
|
- cpuRequest
|
||||||
|
|
Loading…
Reference in New Issue