a0ee569091
follow new naming conventions for gcr's coredns image. starting from 1.21 kubeadm assumes it to be `coredns/coredns`: this causes the kubeadm deployment being unable to pull image, beacuse `v` was also added in image tag, until the role `kubernetes-apps` ovverides it with the old name, which is only compatible with <=1.7. Backward comptability with kubeadm <=1.20 is mantained checking kubernetes version and falling back to old names (`coredns:1.xx`) when the version is less than 1.21
26 lines
684 B
Django/Jinja
26 lines
684 B
Django/Jinja
apiVersion: kubeadm.k8s.io/v1beta2
|
|
kind: InitConfiguration
|
|
nodeRegistration:
|
|
criSocket: {{ cri_socket }}
|
|
---
|
|
apiVersion: kubeadm.k8s.io/v1beta2
|
|
kind: ClusterConfiguration
|
|
imageRepository: {{ kube_image_repo }}
|
|
kubernetesVersion: {{ kube_version }}
|
|
etcd:
|
|
{% if etcd_kubeadm_enabled %}
|
|
local:
|
|
imageRepository: "{{ etcd_image_repo | regex_replace("/etcd$","") }}"
|
|
imageTag: "{{ etcd_image_tag }}"
|
|
{% else %}
|
|
external:
|
|
endpoints:
|
|
{% for endpoint in etcd_access_addresses.split(',') %}
|
|
- {{ endpoint }}
|
|
{% endfor %}
|
|
{% endif %}
|
|
dns:
|
|
type: CoreDNS
|
|
imageRepository: {{ coredns_image_repo | regex_replace('/coredns.*$','') }}
|
|
imageTag: {{ coredns_image_tag }}
|