#22891: adds helm deploy

## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ X ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> added Helm chart configuration for Kubernetes deployments with security-hardened pod settings and `.dockerignore` entry for helm directory **Changes:** - added `helm/` to `.dockerignore` to exclude from Docker builds - created Helm chart with service account, deployment, PVC, secrets, and optional HTTPRoute - configured pod security (non-root user 1000, read-only root filesystem, dropped capabilities, seccomp) - default auth uses auto-generated credentials via `gateway-auth-secret.yaml` with `lookup` to preserve existing values **Issues:** - command path uses `dist/index.js` but Dockerfile CMD uses `openclaw.mjs` (will cause startup failure) - config mount at `/home/node/.openclaw/openclaw.json` conflicts with data volume at `/home/node/.openclaw` (config will be hidden) - default `tag: latest` risks inconsistent deployments <h3>Confidence Score: 1/5</h3> - This PR has critical runtime errors that will prevent the gateway from starting - The incorrect command path (`dist/index.js` vs `openclaw.mjs`) will cause immediate startup failure, and the volume mount conflict will prevent the config file from being read even if the command path is fixed - Pay close attention to `helm/openclaw/values.yaml` (command path) and `helm/openclaw/templates/deployment.yaml` (volume mount conflict) _{Last reviewed commit: b72638d} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->