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
..
api-server-configmap.yaml	feat: add Open WebUI with Tailscale exposure	2026-05-06 15:36:27 +00:00
configmap.yaml	fix: hermes-webui container start failure due to PodSecurity restricted policy	2026-05-07 14:52:13 +00:00
deployment.yaml	fix: hermes-webui container start failure due to PodSecurity restricted policy	2026-05-07 14:52:13 +00:00
hermes-secret.yaml	activate hermes agent	2026-04-25 21:02:14 +00:00
hermes-service.yaml	feat: add Open WebUI with Tailscale exposure	2026-05-06 15:36:27 +00:00
hermes-webui-service.yaml	feat: replace Open WebUI with native Hermes WebUI	2026-05-06 19:33:38 +00:00
kustomization.yaml	feat: replace Open WebUI with native Hermes WebUI	2026-05-06 19:33:38 +00:00
rays-deployment.yaml	fix: copy ConfigMap to PVC on startup so Hermes config is writable	2026-05-06 03:07:30 +00:00
rays-hermes-secret.yaml	fix node selector for 6000pro	2026-04-28 23:16:51 +00:00