add securityContext to allow running with strict PSP (#11547)

Signed-off-by: David J. M. Karlsen <david@davidkarlsen.com>
This commit is contained in:
David J. M. Karlsen
2019-02-19 11:13:54 -08:00
committed by Kubernetes Prow Robot
parent 294d448c6d
commit 85c63f053e
4 changed files with 14 additions and 1 deletions
+1 -1
View File
@@ -3,7 +3,7 @@ appVersion: "1.0.0"
home: https://comcast.github.io/kuberhealthy/
description: The official Helm chart for Kuberhealthy.
name: kuberhealthy
version: 1.0.2
version: 1.1.0
maintainers:
- name: integrii
email: eric.greer@comcast.com
+5
View File
@@ -54,6 +54,11 @@ deployment:
maxUnavailable: 1
imagePullPolicy: IfNotPresent
namespace: kuberhealthy
securityContext: # default container security context
runAsNonRoot: true
runAsUser: 999
fsGroup: 999
allowPrivilegeEscalation: false
```
@@ -30,6 +30,8 @@ spec:
automountServiceAccountToken: true
containers:
- image: {{ .Values.image.repository }}:{{ .Values.image.tag }}
securityContext:
{{- toYaml .Values.securityContext | nindent 10 -}}
imagePullPolicy: {{ .Values.deployment.imagePullPolicy }}
livenessProbe:
failureThreshold: 3
+6
View File
@@ -31,6 +31,12 @@ deployment:
maxUnavailable: 1
imagePullPolicy: IfNotPresent
securityContext:
runAsNonRoot: true
runAsUser: 999
fsGroup: 999
allowPrivilegeEscalation: false
# Please remember that changing the service type to LoadBalancer
# will expose Kuberhealthy to the internet, which could cause
# error messages shown by Kuberhealthy to be exposed to the