add init container option to helm chart (#62)

Author: matheuscscp

helm/gke-metadata-server/Chart.yaml

@@ -30,7 +30,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.2.0
+version: 0.2.1
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

helm/gke-metadata-server/templates/daemonset.yaml

@@ -47,6 +47,10 @@ spec:
       priorityClassName: {{ .Values.priorityClass }}
       hostNetwork: {{ .Values.hostNetwork }}
       dnsPolicy: ClusterFirstWithHostNet
+      {{- if .Values.initContainers }}
+      initContainers:
+      {{- toYaml .Values.initContainers | nindent 6 }}
+      {{- end }}
       containers:
       - name: server
         {{- if .Values.image.digest }}

helm/gke-metadata-server/values.yaml

@@ -80,3 +80,10 @@ priorityClass: system-node-critical
 
 # This Pod needs to listen on the host network, port 80.
 hostNetwork: true
+
+# Pod .spec.initContainers. Can be used for initializing the Node loopback interface
+# with the the Google Metadata IP address (169.254.169.254) using the CLI "init-network"
+# command (see k8s/test-pod.yaml). This allows your pods to run without the sidecar,
+# but also requires the emulator to listen on port 80 (in the host network!). Please
+# assess the risk of opening port 80 in your Nodes before choosing this approach.
+initContainers: