kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #15584 from agilgur5/docs-remove-kube-dns-autoscaler 

docs: remove `kube-dns-autoscaler` when upgrading to CoreDNS
This commit is contained in:
Kubernetes Prow Robot 2023-07-02 20:56:51 -07:00 committed by GitHub
parent 79c964995c 8aa2314420
commit e363128184
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/cluster_spec.md
View File

@ -244,7 +244,7 @@ etcdClusters:
### etcd backups retention
{{ kops_feature_table(kops_added_default='1.18') }}
As of kOps 1.27, the default etcd backup retention duration is 90 days.
As of kOps 1.27, the default etcd backup retention duration is 90 days.
You can adjust the retention duration using the `backupRetentionDays` parameter:
```yaml
@ -847,12 +847,13 @@ This block contains configurations for [CoreDNS](https://coredns.io/).
For Kubernetes version >= 1.20, `CoreDNS` will be installed as the default DNS server.
```yaml
```yaml
spec:
kubeDNS:
provider: CoreDNS
```
OR
```yaml
spec:
kubeDNS:
@ -860,7 +861,7 @@ spec:
Specifying KubeDNS will install kube-dns as the default service discovery instead of [CoreDNS](https://coredns.io/).
```yaml
```yaml
spec:
kubeDNS:
provider: KubeDNS
@ -902,7 +903,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, and then remove both deployments. 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.
For larger clusters you may need to set custom resource requests and limits. For the CoreDNS provider you can set