OpenClaw（网关）的Helm Chart。部署单实例StatefulSet，具备持久存储、秘密管理及可选LiteLLM代理用于模型路由。

要求

• Helm v3
• 支持PersistentVolume的Kubernetes集群（若禁用持久化则为可选）

安装

图表以 GHCR 中的 OCI 工件形式发布。

1）通过@BotFather创建Telegram机器人：

• 给@BotFather消息，发送/newbot，并按照提示操作
• 保存标记：export telegramBotToken=

1）生成网关令牌：

1）安装图表：

它部署了 OpenClaw 网关和带有 Github Copilot 提供者的 LiteLLM 代理（默认启用）。

1） （替代方案）使用特定的模型提供者（例如Anthropic）：

1）访问门户：

然后在浏览器中打开。

1） （可选） 通过 noVNC 查看 Chrome 浏览器的图形界面：

然后在浏览器中打开，查看Chrome桌面。

浏览器图形界面

Chrome 在虚拟显示中以头模式运行。通过 noVNC 访问 kovnc，访问 6080* 端口，实时观看浏览器自动化。

工作原理

supervisord 管理容器内的完整 GUI 堆栈：

1. Xvfb — 虚拟帧缓冲区（显示:99）

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: