1418fb394b
When DNSMasq is configured to read its settings
from a folder ('-7' or '--conf-dir' option) it only
checks that the directory exists and doesn't fail if
it's empty. It could lead to a situation when DNSMasq
is running and handles requests, but not properly
configured, so some of queries can't be resolved.
57 lines
1.5 KiB
YAML
57 lines
1.5 KiB
YAML
---
|
|
apiVersion: extensions/v1beta1
|
|
kind: DaemonSet
|
|
metadata:
|
|
name: dnsmasq
|
|
namespace: "{{system_namespace}}"
|
|
labels:
|
|
k8s-app: dnsmasq
|
|
spec:
|
|
template:
|
|
metadata:
|
|
labels:
|
|
k8s-app: dnsmasq
|
|
spec:
|
|
containers:
|
|
- name: dnsmasq
|
|
image: "{{ dnsmasq_image_repo }}:{{ dnsmasq_image_tag }}"
|
|
imagePullPolicy: {{ k8s_image_pull_policy }}
|
|
command:
|
|
- dnsmasq
|
|
args:
|
|
- -k
|
|
- -C
|
|
- /etc/dnsmasq.d/01-kube-dns.conf
|
|
securityContext:
|
|
capabilities:
|
|
add:
|
|
- NET_ADMIN
|
|
imagePullPolicy: IfNotPresent
|
|
resources:
|
|
limits:
|
|
cpu: {{ dns_cpu_limit }}
|
|
memory: {{ dns_memory_limit }}
|
|
requests:
|
|
cpu: {{ dns_cpu_requests }}
|
|
memory: {{ dns_memory_requests }}
|
|
ports:
|
|
- name: dns
|
|
containerPort: 53
|
|
protocol: UDP
|
|
- name: dns-tcp
|
|
containerPort: 53
|
|
protocol: TCP
|
|
volumeMounts:
|
|
- name: etcdnsmasqd
|
|
mountPath: /etc/dnsmasq.d
|
|
- name: etcdnsmasqdavailable
|
|
mountPath: /etc/dnsmasq.d-available
|
|
|
|
volumes:
|
|
- name: etcdnsmasqd
|
|
hostPath:
|
|
path: /etc/dnsmasq.d
|
|
- name: etcdnsmasqdavailable
|
|
hostPath:
|
|
path: /etc/dnsmasq.d-available
|
|
dnsPolicy: Default # Don't use cluster DNS.
|