Fix calico name resolution (#5291)

5 years ago · 97764921ed
3 changed files with 0 additions and 3 deletions
--- a/roles/kubernetes-apps/policy_controller/calico/templates/calico-kube-controllers.yml.j2
+++ b/roles/kubernetes-apps/policy_controller/calico/templates/calico-kube-controllers.yml.j2
@ -25,7 +25,6 @@ spec:
      nodeSelector:
        beta.kubernetes.io/os: linux
      hostNetwork: true
-      dnsPolicy: ClusterFirstWithHostNet
      serviceAccountName: calico-kube-controllers
      tolerations:
        - key: CriticalAddonsOnly
--- a/roles/network_plugin/calico/templates/calico-node.yml.j2
+++ b/roles/network_plugin/calico/templates/calico-node.yml.j2
@ -27,7 +27,6 @@ spec:
    spec:
      priorityClassName: system-node-critical
      hostNetwork: true
-      dnsPolicy: ClusterFirstWithHostNet
      serviceAccountName: calico-node
      tolerations:
        - effect: NoExecute
--- a/roles/network_plugin/calico/templates/calico-typha.yml.j2
+++ b/roles/network_plugin/calico/templates/calico-typha.yml.j2
@ -54,7 +54,6 @@ spec:
      nodeSelector:
        beta.kubernetes.io/os: linux
      hostNetwork: true
-      dnsPolicy: ClusterFirstWithHostNet
      tolerations:
        # Mark the pod as a critical add-on for rescheduling.
        - key: CriticalAddonsOnly