For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Version support
Review what a kagent release includes, which Kubernetes version it is tested against, and which upgrades are supported.
Only the latest kagent release is supported. The versions on this page apply to that release.
What a kagent release includes
The kagent Helm chart pulls in Agent SubstrateAgent SubstrateThe runtime that kagent runs agents on. It multiplexes many sandboxed Actors onto a smaller pool of pre-started Workers, suspending idle ones to snapshots.Learn more and two other components as subcharts, 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-alpha1 | The controller, the gRPC API, and the agent runtimes. |
| Agent Substrate | 0.2.0-beta4 | The ActorActorThe sandboxed unit of compute, provided by Agent Substrate, that runs an AgentInstance's conversation loop. Every AgentInstance is backed by one.Learn more runtime that every agent runs on, including sandboxing, snapshots, and the WorkerPoolWorkerPoolA Kubernetes custom resource declaring how many Workers to keep running and which sandbox class they use. An operator must provision one before any Harness can create AgentInstances.Learn more. |
| kmcp | 0.3.0 | The MCP server toolkit and its controller. |
| kagent-tools | 0.2.1 | 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, which pins the kindest/node image that CI 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.
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. For the resources that 1.0 replaces or removes, see Release notes.