Harden pod and container security contexts across all workloads
Add securityContext hardening (runAsNonRoot, readOnlyRootFilesystem, capabilities drop ALL, allowPrivilegeEscalation false) to the 10 workloads that lacked it: apache-tika, cyberchef, gotenberg, homeassistant, matrix-delegation-nginx, paperless-server, paperless-consume cronjob (plus automountServiceAccountToken false), patchmon-frontend, urlaubsverwaltung and zipline. All contexts are configurable via securityContext.pod / securityContext.container in values.yaml; writable paths are provided as emptyDirs. Image-forced deviations (Home Assistant root start for s6-overlay + NET_RAW for discovery, paperless root init container for /run ownership) are documented in the charts' values.yaml. Major version bump for every changed published chart.
This commit is contained in:
31 files changed
+357
-16
No files matched your search
@@ -17,10 +17,14 @@ spec:
|
||||
name: "{{ .Release.Name }}-{{ .Chart.Name }}-sfs"
|
||||
spec:
|
||||
automountServiceAccountToken: false
|
||||
securityContext:
|
||||
{{- toYaml .Values.securityContext.pod | nindent 8 }}
|
||||
containers:
|
||||
- name: "{{ .Release.Name }}-{{ .Chart.Name }}"
|
||||
image: "ghcr.io/home-assistant/home-assistant:{{ .Chart.AppVersion }}"
|
||||
imagePullPolicy: IfNotPresent
|
||||
securityContext:
|
||||
{{- toYaml .Values.securityContext.container | nindent 12 }}
|
||||
env:
|
||||
- name: TZ
|
||||
value: "{{ .Values.core.timezone }}"
|
||||
@@ -56,7 +60,17 @@ spec:
|
||||
- mountPath: /config
|
||||
name: hass-volume
|
||||
subPath: hass-config
|
||||
# Writable emptyDirs so the root filesystem can stay read-only:
|
||||
# s6-overlay needs /run, Home Assistant writes temp files to /tmp.
|
||||
- mountPath: /tmp
|
||||
name: tmp
|
||||
- mountPath: /run
|
||||
name: run
|
||||
volumes:
|
||||
- name: tmp
|
||||
emptyDir: {}
|
||||
- name: run
|
||||
emptyDir: {}
|
||||
- name: core-config
|
||||
secret:
|
||||
secretName: {{ .Release.Name }}-{{ .Chart.Name }}-config-secret
|
||||
|
||||
Reference in new issue
Block a user