Change DNS policy for kubernetes components

According to code apiserver, scheduler, controller-manager, proxy don't
use resolution of objects they created. It's not harmful to change
policy to have external resolver.

Signed-off-by: Sergii Golovatiuk <sgolovatiuk@mirantis.com>
This commit is contained in:
Sergii Golovatiuk 2017-04-20 11:07:34 +02:00
parent e796cdbb27
commit d8aa2d0a9e
4 changed files with 4 additions and 4 deletions

View file

@ -9,7 +9,7 @@ metadata:
spec: spec:
hostNetwork: true hostNetwork: true
{% if kube_version | version_compare('v1.6', '>=') %} {% if kube_version | version_compare('v1.6', '>=') %}
dnsPolicy: ClusterFirstWithHostNet dnsPolicy: ClusterFirst
{% endif %} {% endif %}
containers: containers:
- name: kube-apiserver - name: kube-apiserver

View file

@ -8,7 +8,7 @@ metadata:
spec: spec:
hostNetwork: true hostNetwork: true
{% if kube_version | version_compare('v1.6', '>=') %} {% if kube_version | version_compare('v1.6', '>=') %}
dnsPolicy: ClusterFirstWithHostNet dnsPolicy: ClusterFirst
{% endif %} {% endif %}
containers: containers:
- name: kube-controller-manager - name: kube-controller-manager

View file

@ -8,7 +8,7 @@ metadata:
spec: spec:
hostNetwork: true hostNetwork: true
{% if kube_version | version_compare('v1.6', '>=') %} {% if kube_version | version_compare('v1.6', '>=') %}
dnsPolicy: ClusterFirstWithHostNet dnsPolicy: ClusterFirst
{% endif %} {% endif %}
containers: containers:
- name: kube-scheduler - name: kube-scheduler

View file

@ -8,7 +8,7 @@ metadata:
spec: spec:
hostNetwork: true hostNetwork: true
{% if kube_version | version_compare('v1.6', '>=') %} {% if kube_version | version_compare('v1.6', '>=') %}
dnsPolicy: ClusterFirstWithHostNet dnsPolicy: ClusterFirst
{% endif %} {% endif %}
containers: containers:
- name: kube-proxy - name: kube-proxy