helm: added necessary hostPorts in the PodSecurityPolicy (#371)

When metric/prometheus endpoint is enabled, we currently have an issue as the
PodSecurityPolicy does not allow the pod to bind the ports. This change sorts
this issue out (#365).

Signed-off-by: Maxime VISONNEAU <[email protected]>

Author: mvisonneau

config/helm/aws-node-termination-handler/templates/psp.yaml

@@ -12,6 +12,11 @@ spec:
   hostIPC: false
   hostNetwork: {{ .Values.useHostNetwork }} 
   hostPID: false
+{{- if and .Values.rbac.pspEnabled .Values.enablePrometheusServer }}
+  hostPorts:
+  - min: {{ .Values.prometheusServerPort }}
+    max: {{ .Values.prometheusServerPort }}
+{{- end }}
   readOnlyRootFilesystem: false
   allowPrivilegeEscalation: false
   allowedCapabilities:

config/helm/aws-node-termination-handler/test.yaml

@@ -122,7 +122,7 @@ windowsNodeSelector: {
 }
 
 enablePrometheusServer: true
-prometheusServerPort: "9092"
+prometheusServerPort: 9092
 
 tolerations:
 - operator: "Exists"

config/helm/aws-node-termination-handler/values.yaml

@@ -142,7 +142,7 @@ nodeSelectorTermsOs: ""
 nodeSelectorTermsArch: ""
 
 enablePrometheusServer: false
-prometheusServerPort: "9092"
+prometheusServerPort: 9092
 
 tolerations:
   - operator: "Exists"