Deploy OpenClaw as a single-pod gateway on your existing Kubernetes cluster. This template includes everything you need to get OpenClaw running: a dedicated namespace, Kubernetes Secrets for your API tokens, persistent storage for config and workspace data, a Deployment with liveness and readiness probes, a ClusterIP Service, and an Ingress configured with extended WebSocket timeouts so long-running sessions do not get cut off. Apply all manifests in one command or walk through them one by one.
Components
- Namespace
- Secret (Telegram, Anthropic, Discord API tokens)
- PersistentVolumeClaim x2 (config 10Gi + workspace 20Gi)
- Deployment (single replica, liveness/readiness probes)
- Service (ClusterIP)
- Ingress (NGINX, 3600s WebSocket timeouts, cert-manager TLS)
Use Case
You want to run OpenClaw for your team without spinning up a separate VM. You already have a Kubernetes cluster with some spare capacity and want a clean, declarative setup that Kubernetes can self-heal if the pod crashes.
