add support for dnsPolicy (#174)

gruntwork-io · Aug 10, 2023 · 75c2eb8 · 75c2eb8
1 parent bd10fee
commit 75c2eb8
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/charts/k8s-service/templates/_deployment_spec.tpl b/charts/k8s-service/templates/_deployment_spec.tpl
@@ -145,6 +145,10 @@ spec:
 {{ toYaml .Values.hostAliases | indent 8 }}
       {{- end }}
 
+      {{- if .Values.dnsPolicy }}
+      dnsPolicy: {{ .Values.dnsPolicy }}
+      {{- end }}
+
       containers:
         {{- if .isCanary }}
         - name: {{ .Values.applicationName }}-canary

diff --git a/charts/k8s-service/values.yaml b/charts/k8s-service/values.yaml
@@ -76,6 +76,14 @@ containerPorts:
     port: 80
     protocol: TCP
 
+# dnsPolicy sets the Pod DNS policy. Allowed values are "Default", "ClusterFirst", "ClusterFirstWithHostNet" (not supported on Windows), 
+# and "None". Note that "Default" is not the default DNS policy. If dnsPolicy is not explicitly specified, then "ClusterFirst" is used.
+# See [Pod's DNS Policy](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy) for details.
+#
+# EXAMPLE:
+#
+# dnsPolicy: "ClusterFirst"
+
 # startupProbe is a map that specifies the startup probe of the main application container. Startup probes indicate
 # when a container application has started. If such a probe is configured, it disables liveness and readiness checks
 # until it succeeds, making sure those probes don't interfere with the application startup. This can be used to adopt