From 7b250b5cc477c0b951f2d412f22b69641b485e76 Mon Sep 17 00:00:00 2001
From: Mark Burnett <mark.m.burnett@gmail.com>
Date: Tue, 12 Dec 2017 16:02:11 -0600
Subject: [PATCH] Fix: change bootstrapping CoreDNS Pod labels

Exclude the host bootstrapping coredns pod from the Kubernetes DNS
Service, so that no traffic is routed to it until the node is joined.

Change-Id: Ic0ac97d343b08f49ef6034fa186766fe17ab1738
---
 .../roles/common/etc/kubernetes/manifests/coredns.yaml       | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/promenade/templates/roles/common/etc/kubernetes/manifests/coredns.yaml b/promenade/templates/roles/common/etc/kubernetes/manifests/coredns.yaml
index dfefed0a..3cd0a22c 100644
--- a/promenade/templates/roles/common/etc/kubernetes/manifests/coredns.yaml
+++ b/promenade/templates/roles/common/etc/kubernetes/manifests/coredns.yaml
@@ -5,7 +5,10 @@ metadata:
   name: coredns
   namespace: kube-system
   labels:
-    coredns-service: enabled
+    # NOTE(mark-burnett): This is a host initialization Pod and should not be
+    # included in the Kubernetes DNS service, so ensure it does not get
+    # selected.
+    coredns-service: disabled
   annotations:
     scheduler.alpha.kubernetes.io/critical-pod: ''
 spec: