openclaw-kubernetes AGENTS.md

AGENTS.md

This file provides guidance to AI coding agents when working with code in this repository.

Overview

This is a Helm chart repository for deploying OpenClaw (a personal AI assistant gateway) to Kubernetes. The chart deploys two components: an OpenClaw StatefulSet (single-instance, persistent storage) and an optional LiteLLM proxy Deployment for model provider decoupling. It also includes a Dockerfile for the OpenClaw container image.

Links

• OpenClaw (formerly Moltbot/Clawdbot)
• Source Code

Development Commands

# Lint the chart against all values files
./scripts/helm-lint.sh

# Render templates to verify correctness (output discarded)
./scripts/helm-test.sh

# Render templates to stdout for inspection
helm template openclaw . -f values.yaml

# Render with a specific values file
helm template openclaw . -f values-production.yaml --set secrets.openclawGatewayToken=test

# Lint with chart-testing tool (used in CI)
ct lint --config ct.yaml

# Package and publish chart to GHCR (requires authentication)
helm registry login ghcr.io -u <username> -p <token>
./scripts/publish-chart.sh

All lint/test scripts pass --set secrets.openclawGatewayToken=lint-token automatically to satisfy the required secret validation.

Version Bump

Follow these steps to release a new chart version:

1. Update chart version — Bump version and appVersion in Chart.yaml (e.g., 0.1.11 → 0.1.12).
2. Update changelog — Run git log v<previous>..HEAD --oneline to list all commits since the last version tag. For any merge commits (e.g., Merge pull request #N), also inspect the individual commits they brought in (git log v<previous>..HEAD --oneline will include them). Ensure every non-version-bump commit — including those introduced via merged PRs — is reflected in CHANGELOG.md. Add a summary following the existing format (date, bullet points describing changes).
3. Commit — Stage Chart.yaml and CHANGELOG.md, commit with message chore: bump chart version to <new-version>.
4. Tag — Create an annotated tag: git tag v<new-version>.
5. Push — Ask the user whether to push the main branch and new tag (git push origin main && git push origin v<new-version>).