> For the complete documentation index, see [llms.txt](https://docs.zenml.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenml.io/kitaru/getting-started/deploy/helm.md).

# Helm

Deploy the Kitaru server on Kubernetes with the first-party Helm chart, covering external Postgres, automatic migrations, ingress, and TLS.

The repository ships a first-party chart under `helm/` that deploys the Kitaru server on Kubernetes: a server Deployment (with optional autoscaling), a Service, ingress or Gateway API routing, and a database migration Job that runs before each install and upgrade so the server never starts against an unmigrated schema.

The chart deploys **the server only**. Postgres is yours to provide (managed Postgres is the expected shape), and [workers](/kitaru/running-in-production/workers.md) deploy separately in the environments your agents run in.

```bash
helm install kitaru oci://public.ecr.aws/zenml/kitaru \
  --namespace kitaru --create-namespace \
  --values my-values.yaml
```

## The values that matter

A minimal production `my-values.yaml`:

```yaml
server:
  serverURL: https://kitaru.internal.example.com

  database:
    host: your-postgres-host
    username: kitaru
    passwordSecretRef:
      name: kitaru-db
      key: password
    sslMode: require

  auth:
    authScheme: local
    defaultAccount:
      passwordSecretRef:
        name: kitaru-bootstrap
        key: password

ingress:
  enabled: true
  host: kitaru.internal.example.com
```

The chart mirrors the same `KITARU_SERVER_*` configuration surface as the [Docker deployment](/kitaru/getting-started/deploy/docker.md): every server setting has a values path, secrets can be inline for a quick start or `secretRef`s for real deployments, and database TLS supports `disable` through `verify-full` with custom CA bundles.

The image is the published `zenmldocker/kitaru-server`, tagged to match the chart version by default; pin `server.image.tag` explicitly if you want upgrades to be deliberate.

## Operational notes

* **Migrations** run as a Helm hook Job before the server pods roll, so an upgrade that needs a schema change can't race its own pods. If the migration fails, the release fails and the previous version keeps running.
* **Scaling**: the server is stateless between requests; enable the HPA block or set replicas directly. All state is in Postgres.
* **Routing**: classic Ingress (nginx by default) and Gateway API HTTPRoute are both supported; enable exactly one.

After install, point your team at it:

```bash
kitaru login https://kitaru.internal.example.com
kitaru status
```

Then create [accounts and API keys](/kitaru/running-in-production/authentication.md) and start [workers](/kitaru/running-in-production/workers.md) where your agents live.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zenml.io/kitaru/getting-started/deploy/helm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.