Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Upgrade from 2026.09 to 2026.11

IfDo this
You have scheduled agentsAsk the people who created them to switch them off before step 3. Only an agent’s creator can switch it off, using the toggle next to the agent on the My agents tab or the Agent Scheduler toggle when editing it. A run that starts during the upgrade fails and isn’t retried.
Kindo runs QdrantAdd a DNS record for qdrant.<domain>, and make sure a TLS certificate you supply or get from your cloud provider covers it.
Your DNS records or TLS certificate name each Kindo host, rather than using a wildcardAdd DNS records for flagsmith.<domain> and flagsmith-edge.<domain>, unless external-dns publishes your records. Make sure your certificate covers both hosts. The upgrade refuses a certificate in the config that doesn’t cover them.
You route Kindo’s hosts yourself, without Kindo-managed ingressRoute /auth, /trpc and /express on the web app’s host, app.<domain> by default, to the API, or nobody can sign in. Add routes for flagsmith.<domain> and flagsmith-edge.<domain>. See Your own routing.
You use Azure Database for PostgreSQLAdd PG_TRGM to the azure.extensions server parameter on your auxiliary server, or on your main server if you have no auxiliary one, keeping the extensions already listed. See PostgreSQL setup.
Your install contract turns off components other than Qdrant and SpeachesThe upgrade deploys them, so make sure the cluster has room. If a component you turned off runs a version older than 2026.09, turn it back on and upgrade with the 2026.09 CLI.
Your install contract sets an address other than <service>.<domain> for any Kindo host except the web app, webhooks and storage addressesPoint DNS and your routing at the default host, remove that address from the contract, and roll it out with the 2026.09 CLI.
You keep Kindo’s credentials in Vault, AWS Secrets Manager or Azure Key VaultAdd every entry your instance needs from Secret store keys. Flagsmith and each supporting service Kindo runs, such as ClickHouse and RabbitMQ, need one. The upgrade checks them and stops before changing anything if one is missing.
  • Plan one maintenance window for the whole upgrade.
  • Make sure the cluster’s control plane and every node run Kubernetes 1.32 or later. The upgrade stops if any of them is older.
  • Make sure every Kindo component runs the same patch of the 2026.09 release line. If not, upgrade to the latest 2026.09 patch with the 2026.09 CLI first.
  • Make sure no Kindo component is partway through being installed, upgraded or removed.

Make sure your workstation has the tools the new version needs, and Helm’s diff plugin at 3.15.0 or later.

Check the version of any diff plugin you already have:

Terminal window
helm plugin list

Remove a version earlier than 3.15.0:

Terminal window
helm plugin uninstall diff

Install the plugin if you don’t have it or you removed it. Helm checks plugin signatures and can’t check a plugin installed straight from its Git repository, so the command skips that check. To install a signed release instead, follow helm-diff’s installation steps.

Terminal window
helm plugin install https://github.com/databus23/helm-diff --version v3.15.15 --verify=false

Back up your external databases and object storage with your own backup tools. Then back up the data in the cluster.

4. Back up the config with the 2026.09 CLI

Section titled “4. Back up the config with the 2026.09 CLI”

Run the backup from the directory that holds your install contract and environment bindings files. Keep them with the backup. These backups are the only way back to 2026.09.

Terminal window
kindo config backup --output kindo-2026.09-pre-upgrade.bundle

Install it as the user who runs it, not as root. Use 2026.11.0, or a later 2026.11 version if one is out. On macOS or without uv, follow Update or switch the CLI instead.

Log in with the registry username and password Kindo provided:

Terminal window
helm registry login registry.kindo.ai --username '<registry-username>'

Download the CLI:

Terminal window
download="$(mktemp -d)"
helm pull oci://registry.kindo.ai/kindo-cli/kindo-cli --version 2026.11.0 --untar --untardir "$download"

Check the download:

Terminal window
(cd "$download/kindo-cli" && sha256sum -c SHA256SUMS)

Install the CLI with uv:

Terminal window
uv tool install --force "$download"/kindo-cli/kindo_cli-*.whl

Check its version. It should report the version you downloaded.

Terminal window
kindo --version

If it reports another version, or the command isn’t found, follow Update or switch the CLI.

The config migration can’t be undone, so make sure you have the backups from steps 3 and 4.

Migrate the config from the directory that holds your install contract and environment bindings files:

Terminal window
kindo config migrate

Answer yes only if the question names your cluster.

From here on, use the 2026.11 CLI.

7. Make the config changes that apply to you

Section titled “7. Make the config changes that apply to you”

Move any change you made directly to a Kubernetes object into the config, or the upgrade resets it. If you relied on the global log level, set a log level for each application instead. See How the config works.

Don’t change the PostgreSQL servers the config migration wrote until the upgrade finishes.

Terminal window
kindo upgrade
Terminal window
kindo config backup --output kindo-2026.11-$(date +%F).bundle

Copy the flags:

Terminal window
kindo feature-flags migrate

Answer yes only if the question names your cluster.

If the copy says some flags aren’t served yet, wait a few minutes and run the copy again.

If the copy tells you to create flags in Flagsmith, create them, then run the copy again. Check any other flag it lists in Flagsmith.

Switch Kindo’s applications to Flagsmith:

Terminal window
kindo config apply

Answer yes only if it changes just the four applications that read feature flags: api, next, credits, and task-worker-ts. They switch to Flagsmith. If it changes anything else, answer no and contact Kindo support. When it finishes, it reports four changes.

Make sure the check reports nothing critical:

Terminal window
kindo status
kindo doctor

Then run the Verify checks, and compare your dashboards with your usual error rates.

If you have scheduled agents, tell the people who created them they can switch them back on.

If the upgrade stops before it finishes, fix the cause and run it again before you roll back. To roll back, follow Roll back a release line.

If you have scheduled agents, tell the people who created them they can switch them back on.