Hermes Agent d2f011956e fix: hermes-webui container start failure due to PodSecurity restricted policy ... - Updated pod.spec.securityContext and all container/initContainer securityContext to be fully compliant with restricted:latest (runAsNonRoot: true, allowPrivilegeEscalation: false, runAsUser: 1000, capabilities drop ALL, seccomp RuntimeDefault, fsGroup) - Changed initContainer from root chown to non-root mkdir/chmod relying on fsGroup (avoids PSA violation) - Updated default model to grok-4.20-0309-reasoning (per xAI switch note) - Added automountServiceAccountToken: false and imagePullPolicy for best practices (matches openclaw deployment pattern) - hermes-webui now runs as non-root with WANTED_UID matching This should resolve the container not starting. Leave PR open for review before merge.		2026-05-07 14:52:13 +00:00
..
customer1	fix: hermes-webui container start failure due to PodSecurity restricted policy	2026-05-07 14:52:13 +00:00
monitoring/dashboards	add dashboards to namespace	2026-05-04 20:38:22 +00:00