don't set securitycontext on openshift/okd

If running on OpenShift, these settings cause problems because the user and group ids are below the range openshift expects. If not specified, they're automatically handled by OpenShift.
hashicorp · Jun 25, 2022 · 04acc2a · 04acc2a
1 parent 9b7425a
commit 04acc2a
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/charts/consul/templates/gossip-encryption-autogenerate-job.yaml b/charts/consul/templates/gossip-encryption-autogenerate-job.yaml
@@ -32,11 +32,13 @@ spec:
     spec:
       restartPolicy: Never
       serviceAccountName: {{ template "consul.fullname" . }}-gossip-encryption-autogenerate
+      {{- if not .Values.global.openshift.enabled }}
       securityContext:
         runAsNonRoot: true
         runAsGroup: 1000 
         runAsUser: 100 
         fsGroup: 1000
+      {{- end }}
       containers:
         - name: gossip-encryption-autogen
           image: "{{ .Values.global.imageK8S }}"