Update CoreDNS to 1.6.7 (#5761)
parent
dcfda9d9d2
commit
027e2e8a11
|
@ -131,7 +131,7 @@ Note: Upstart/SysV init based OS types are not supported.
|
|||
- [cephfs-provisioner](https://github.com/kubernetes-incubator/external-storage) v2.1.0-k8s1.11
|
||||
- [rbd-provisioner](https://github.com/kubernetes-incubator/external-storage) v2.1.1-k8s1.11
|
||||
- [cert-manager](https://github.com/jetstack/cert-manager) v0.11.0
|
||||
- [coredns](https://github.com/coredns/coredns) v1.6.0
|
||||
- [coredns](https://github.com/coredns/coredns) v1.6.7
|
||||
- [ingress-nginx](https://github.com/kubernetes/ingress-nginx) v0.28.0
|
||||
|
||||
Note: The list of validated [docker versions](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.16.md) was updated to 1.13.1, 17.03, 17.06, 17.09, 18.06, 18.09. kubeadm now properly recognizes Docker 18.09.0 and newer, but still treats 18.06 as the default supported version. The kubelet might break on docker's non-standard version numbering (it no longer uses semantic versioning). To ensure auto-updates don't break your cluster look into e.g. yum versionlock plugin or apt pin).
|
||||
|
|
|
@ -429,7 +429,7 @@ nginx_image_tag: 1.17
|
|||
haproxy_image_repo: "{{ docker_image_repo }}/library/haproxy"
|
||||
haproxy_image_tag: 1.9
|
||||
|
||||
coredns_version: "1.6.0"
|
||||
coredns_version: "1.6.7"
|
||||
coredns_image_repo: "{{ docker_image_repo }}/coredns/coredns"
|
||||
coredns_image_tag: "{{ coredns_version }}"
|
||||
|
||||
|
|
Loading…
Reference in New Issue