OpenClaw Helm Chart

Helm chart for OpenClaw (gateway). Deploys a single-instance StatefulSet with persistent storage, secrets management, and an optional LiteLLM proxy for model routing.

Requirements

• Helm v3
• A Kubernetes cluster with PersistentVolume support (optional if persistence is disabled)

Install

Charts are published as OCI artifacts in GHCR.

1. Create a Telegram bot via @BotFather:

   • Message @BotFather, send /newbot, and follow the prompts
   • Save the token: export telegramBotToken=

2. Generate a gateway token:

   export gatewayToken=$(openssl rand -hex 32)
   

3. Install the chart:

   helm install openclaw oci://ghcr.io/feiskyer/openclaw-kubernetes/openclaw \
      --create-namespace --namespace openclaw \
      --set secrets.openclawGatewayToken=$gatewayToken \
      --set secrets.telegramBotToken=$telegramBotToken
   

   This deploys the OpenClaw gateway and a LiteLLM proxy with Github Copilot provider (enabled by default).

4. (Alternative) Use a specific model provider (e.g. Anthropic):

   helm install openclaw oci://ghcr.io/feiskyer/openclaw-kubernetes/openclaw \
      --create-namespace --namespace openclaw \
      --set secrets.openclawGatewayToken=$gatewayToken \
      --set secrets.telegramBotToken=$telegramBotToken \
      --set litellm.secrets.provider=anthropic \
      --set litellm.secrets.apiKey= \
      --set litellm.secrets.apiBase= \
      --set litellm.model=claude-opus-4.6
   

5. Access the portal:

   kubectl --namespace openclaw port-forward openclaw-0 18789:18789
   

   Then open in your browser.

6. (Optional) View the Chrome browser GUI via noVNC:

   kubectl --namespace openclaw port-forward openclaw-0 6080:6080
   

   Then open in your browser to see the Chrome desktop.

Browser GUI

Chrome runs in headed mode inside a virtual display. Access the desktop via noVNC on port 6080 to watch browser automation in real time.

supervisord manages the full GUI stack inside the container:

1. Xvfb — virtual framebuffer (display :99)
2. Fluxbox — lightweight window manager
3. x11vnc — VNC server on port 5900 (localhost only)
4. websockify + noVNC — bridges VNC to WebSocket, served on port 6080
5. OpenClaw gateway — launches Chrome against DISPLAY=:99

All processes auto-restart on failure.

Environment variables: