Rollback coredns, should not have been updated before 1.19 (#6573)
parent
36924b63dc
commit
1ff95e85f4
|
@ -138,7 +138,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.15.2
|
||||
- [coredns](https://github.com/coredns/coredns) v1.7.0
|
||||
- [coredns](https://github.com/coredns/coredns) v1.6.7
|
||||
- [ingress-nginx](https://github.com/kubernetes/ingress-nginx) v0.32.0
|
||||
|
||||
Note: The list of validated [docker versions](https://kubernetes.io/docs/setup/production-environment/container-runtimes/#docker) is 1.13.1, 17.03, 17.06, 17.09, 18.06, 18.09 and 19.03. The recommended docker version is 19.03. 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).
|
||||
|
|
|
@ -531,7 +531,7 @@ haproxy_image_tag: 2.1
|
|||
|
||||
# Coredns version should be supported by corefile-migration (or at least work with)
|
||||
# bundle with kubeadm; if not 'basic' upgrade can sometimes fail
|
||||
coredns_version: "1.7.0"
|
||||
coredns_version: "1.6.7"
|
||||
coredns_image_repo: "{{ docker_image_repo }}/coredns/coredns"
|
||||
coredns_image_tag: "{{ coredns_version }}"
|
||||
|
||||
|
|
Loading…
Reference in New Issue