bbd57d5f5e
Use cloud-init config to replace /etc/resolv.conf with the content for kubelet to properly configure hostnet pods. Do not use systemd-resolved yet, see https://coreos.com/os/docs/latest/configuring-dns.html "Only nss-aware applications can take advantage of the systemd-resolved cache. Notably, this means that statically linked Go programs and programs running within Docker/rkt will use /etc/resolv.conf only, and will not use the systemd-resolve cache." Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
29 lines
762 B
YAML
29 lines
762 B
YAML
---
|
|
# Existing search/nameserver resolvconf entries will be purged and
|
|
# ensured by this additional data:
|
|
|
|
# Max of 4 names is allowed and no more than 256 - 17 chars total
|
|
# (a 2 is reserved for the 'default.svc.' and'svc.')
|
|
#searchdomains:
|
|
# - foo.bar.lc
|
|
|
|
# Max of 2 is allowed here (a 1 is reserved for the dns_server)
|
|
#nameservers:
|
|
# - 127.0.0.1
|
|
|
|
# CoreOS cloud init config file to define /etc/resolv.conf content
|
|
# for hostnet pods and infra needs
|
|
resolveconf_cloud_init_conf: /etc/resolveconf_cloud_init.conf
|
|
|
|
# Versions
|
|
dnsmasq_version: 2.72
|
|
|
|
# Images
|
|
dnsmasq_image_repo: "andyshinn/dnsmasq"
|
|
dnsmasq_image_tag: "{{ dnsmasq_version }}"
|
|
|
|
# Skip dnsmasq setup
|
|
skip_dnsmasq: false
|
|
|
|
# Skip setting up dnsmasq daemonset
|
|
skip_dnsmasq_k8s: "{{ skip_dnsmasq }}"
|