Add securityContext (#2571)

* Update Chart.yaml * Update apiserver-deployment.yaml * Update controller-manager-deployment.yaml * Update values.yaml * Update Chart.yaml go back to previous version as requested by reviewer
kubernetes-retired · Mar 5, 2019 · f627697 · f627697
1 parent 49e5cc4
commit f627697
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 0 deletions.
diff --git a/charts/catalog/templates/apiserver-deployment.yaml b/charts/catalog/templates/apiserver-deployment.yaml
@@ -28,6 +28,10 @@ spec:
 {{ toYaml .Values.apiserver.annotations | indent 8 }}
       {{- end }}
     spec:
+{{- with .Values.securityContext }}
+      securityContext:
+{{ toYaml . | indent 8 }}
+{{- end }}        
       serviceAccountName: "{{ .Values.apiserver.serviceAccount }}"
       containers:
       - name: apiserver

diff --git a/charts/catalog/templates/controller-manager-deployment.yaml b/charts/catalog/templates/controller-manager-deployment.yaml
@@ -28,6 +28,10 @@ spec:
         release: "{{ .Release.Name }}"
         heritage: "{{ .Release.Service }}"
     spec:
+{{- with .Values.securityContext }}
+      securityContext:
+{{ toYaml . | indent 8 }}
+{{- end }}        
       serviceAccountName: "{{ .Values.controllerManager.serviceAccount }}"
       containers:
       - name: controller-manager

diff --git a/charts/catalog/values.yaml b/charts/catalog/values.yaml
@@ -179,3 +179,7 @@ asyncBindingOperationsEnabled: false
 namespacedServiceBrokerDisabled: false
 # Whether the ServicePlanDefaults alpha feature should be enabled
 servicePlanDefaultsEnabled: false
+## Security context give the opportunity to run container as nonroot by setting a securityContext 
+## by example :
+## securityContext: { runAsUser: 1001 }
+securityContext: {}