> For the complete documentation index, see [llms.txt](/docs/llms.txt). Markdown versions of all docs pages are available by appending .md to any docs URL.

# Version support

Only the latest kagent release is supported. The versions on this page apply to that release.

## What a kagent release includes

A kagent release depends on Agent Substrate and on the kagent-tools subchart, each on its own release cadence. Because a kagent release pins one version of each, the pinned versions are the combination that kagent is built and tested against.

| Component | Version | What it provides |
| --- | --- | --- |
| kagent | 1.0.0-alpha16 | The controller, the gRPC API, and the agent runtimes. |
| Agent Substrate | 0.6.0-alpha3 | The Actor runtime that every agent runs on, including sandboxing, snapshots, and the WorkerPool. |
| kagent-tools | 0.3.0 | The bundled tool server that the built-in RemoteMCPServer points at. |

> [!IMPORTANT]
> Do not upgrade Agent Substrate independently of kagent. Substrate folds schema changes into a single baseline migration before its own release, so an existing database keeps its recorded schema version and never applies the change. The cluster then looks healthy, agents answer normally, and every checkpoint operation fails at runtime against a table that was renamed. Install the substrate version that your kagent release pins.

## Kubernetes versions

kagent's CI tests one Kubernetes minor version at a time rather than a matrix, so there is a single tested version rather than a supported range.

kagent's CI tests against Kubernetes 1.35 today. That version is sourced from `KIND_IMAGE_VERSION` in the [kagent Makefile](https://github.com/kagent-dev/kagent/blob/main/Makefile), which pins the [kindest/node](https://hub.docker.com/r/kindest/node) image that [CI](https://github.com/kagent-dev/kagent/blob/main/.github/workflows/ci.yaml) uses.

Other Kubernetes versions are not exercised in CI and are not guaranteed to work. kagent's Kubernetes client libraries generally follow the [client-go version skew policy](https://github.com/kubernetes/client-go#compatibility-matrix).

## Release support and compatibility

kagent 1.0 is a deliberate clean break from the 0.10.x line, and the compatibility promises start rather than continue at 1.0.

| Upgrade path | Supported |
| --- | --- |
| 0.10.x to 1.0 in place | No. An existing 0.10.x database requires a new PostgreSQL database, because there is no migration bridge. |
| 1.0 back to 0.10.x | No. Downgrade across the 1.0 boundary is unsupported. |
| 1.0 forward to a later minor release | Yes. From 1.0 onward, migrations are append-only and each minor release retains compatibility with the previous release line. |

Moving from 0.10.x therefore means standing up a new installation and recreating your resources on it, rather than running `helm upgrade`. For the procedure, see [Upgrade from 0.x](https://kagent.dev/docs/kagent/1.x/operations/upgrade-from-0x#in-place-upgrade-blockers). For the resources that 1.0 replaces or removes, see [Release notes](https://kagent.dev/docs/kagent/1.x/reference/release-notes/1.0#removed-and-replaced-resources).