Skip to main content

Configuration

Agent profiles​

An OpenClaw profile is a set of workspace files stored in an ORAS-compatible registry and copied into the workspace at startup. The repository includes example profiles under profile/.

openclaw:
  secrets:
    - name: GITLAB_TOKEN
      value: glpat-
  git:
    user:
      email: "eugene@example.com"
      name: "Eugene Harold Krabs"
  profile:
    registry: registry.gitlab.com
    repository: xrow-public/helm-openclaw/eugene-harold-krabs

Network access​

Use local port forwarding or expose OpenClaw only on a private network. When your cluster enforces NetworkPolicy, enable the chart policy and allow ingress from the namespace that owns your ingress controller:

openclaw:
  networkPolicy:
    enabled: true
    ingress:
      from:
        - namespaceSelector:
            matchLabels:
              kubernetes.io/metadata.name: ingress-nginx

Persistence​

By default, the chart creates a PersistentVolumeClaim for /mnt/openclaw.

Use an existing claim when restoring data or migrating a workspace:

openclaw:
  persistence:
    existingClaim: openclaw-workspace

Set openclaw.persistence.enabled=false for ephemeral test deployments. The chart then mounts an emptyDir.

Browserless​

The bundled Browserless service is enabled by default for the OpenClaw browser tool. The generated openclaw.json points at the release-scoped Browserless Service name, for example openclaw-browserless.

Set Browserless chart overrides at the subchart root:

browserless:
  image:
    tag: latest
  resources:
    requests:
      cpu: 250m
      memory: 512Mi

If browserless.browserless.token is set, the generated URL includes a ?token= query parameter.