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

Upgrade Kindo

Upgrading from 2026.09? Follow Upgrade from 2026.09 to 2026.11 instead.

  • Plan a maintenance window, and make sure no other Kindo command is running against the cluster.
  • Make sure your workstation has the tools the new version needs.
  • If you mirror the Kindo registry, copy the new version’s images and charts into your mirror.

Use your own backup tools for your external databases, your object storage, and the Qdrant, ClickHouse and HyperDX data.

These backups are the only way back to the version you’re leaving.

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

Follow Update or switch the CLI.

Make the changes the release notes ask for. Move any change you made directly to a Kubernetes object into the config, or the upgrade resets it. Don’t change the PostgreSQL servers in the config: the upgrade refuses it.

Terminal window
kindo upgrade

If your instance has no superadmin yet, the upgrade creates one for your superadmin email and prints its key once at the end. Store it in your password manager.

If a warning names failed steps, run the command the output names.

A CLI restores only backups from its own release line.

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

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 the upgrade stops before it finishes, fix the cause and run it again before you roll back. To go back, see Roll back.