Install Kindo
Preparation for some instances
Section titled “Preparation for some instances”| If | Do this |
|---|---|
| Your workstation has less than 2 GiB of memory | Before you run any Kindo command, lower concurrency in your shell with export KINDO_CONCURRENCY=2. If a command still runs out of memory, set it to 1. |
| You use your own secrets manager | Give Kindo access to it and create its entries, as Secret store describes. |
| You reach AWS Bedrock with an IAM role | Set up the role, as AI models describes. |
Prepare your workstation
Section titled “Prepare your workstation”1. Check your workstation
Section titled “1. Check your workstation”Your workstation is the machine you run the Kindo CLI from. It needs these tools:
| Tool | Version | Note |
|---|---|---|
kubectl | 1.32+ | |
helm | 4+ | |
Helm’s diff plugin | 3.15.0+ | |
helmfile | 1.2+ | |
bash, curl, jq, openssl | any | |
python3 | any | Must be on your path even if the CLI runs on a Python of its own |
| Python | 3.11+ | For the CLI itself |
uv | any | Recommended for installing the CLI |
psql | any | Only for opening a database prompt or resetting a database |
Installing the CLI needs PyPI or your PyPI mirror. If the workstation can reach neither, ask Kindo support for the CLI’s dependencies.
| Minimum | Recommended | |
|---|---|---|
| CPU | 2 vCPU, with steady performance | 2 vCPU, not burstable |
| Memory | 2 GiB, or 1 GiB with lower concurrency | 4 GiB |
| Free disk | 2 GiB | 10 GiB |
| Network | Reaches the cluster’s API server and the registry | In the same region or network as the cluster |
Don’t use a burstable virtual machine that throttles: once it has used up its CPU credits, an upgrade can take hours.
2. Get Helm’s diff plugin
Section titled “2. Get Helm’s diff plugin”Check the version of any diff plugin you already have:
helm plugin listRemove a version earlier than 3.15.0:
helm plugin uninstall diffInstall 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.
helm plugin install https://github.com/databus23/helm-diff --version v3.15.15 --verify=false3. Check that you can reach the cluster
Section titled “3. Check that you can reach the cluster”Show the cluster your context points at:
kubectl cluster-infoCheck your permissions. The answer must be yes:
kubectl auth can-i create namespace --all-namespaces4. Download and check the CLI
Section titled “4. Download and check the CLI”Each CLI installs its own version. In the commands below, replace the version placeholder with the version you want, such as 2026.11.0.
Log in with the registry username and password Kindo provided:
helm registry login registry.kindo.ai --username '<registry-username>'Download the CLI:
download="$(mktemp -d)"helm pull oci://registry.kindo.ai/kindo-cli/kindo-cli --version <version> --untar --untardir "$download"Check the download. On Linux:
(cd "$download/kindo-cli" && sha256sum -c SHA256SUMS)On macOS:
(cd "$download/kindo-cli" && shasum -a 256 -c SHA256SUMS)5. Install the CLI
Section titled “5. Install the CLI”Install it as the user who runs it, not as root.
With uv (recommended), install the CLI:
uv tool install --force "$download"/kindo-cli/kindo_cli-*.whlCheck its version. It should report the version you downloaded.
kindo --versionIf it reports another version, or the command isn’t found, put uv’s tool folder first on your path:
export PATH="$HOME/.local/bin:$PATH"Without uv, do the rest of this step instead. Check that Python is 3.11 or newer:
python3 --versionInstall with uv instead if it’s older.
Create a Python environment for the CLI. On Debian or Ubuntu, install the Python venv package first:
sudo apt-get install python3-venvpython3 -m venv "$HOME/.kindo-cli"Install the CLI into it:
"$HOME/.kindo-cli/bin/pip" install "$download"/kindo-cli/kindo_cli-*.whlPut the CLI on your path by adding its folder to the front:
export PATH="$HOME/.kindo-cli/bin:$PATH"Check its version. It should report the version you downloaded.
kindo --versionCreate your config
Section titled “Create your config”6. Gather what the config needs
Section titled “6. Gather what the config needs”Have these ready:
- Service addresses and logins. For everything on Infrastructure: the address and login for each.
- Base domain. The domain Kindo’s addresses sit under.
- Superadmin email. The superadmin signs in with codes sent to it.
- Registry login. The username and password for the Kindo registry that Kindo provided.
- Routing, DNS, and TLS. Ready as Routing, DNS, and TLS lists them.
- Object storage sign-in. An access key, or a cloud identity such as an IAM role.
7. Create your config
Section titled “7. Create your config”Create your config one of two ways.
To answer questions, run this, then skip to Turn off response buffering for chat:
kindo config initTo fill in a template, do the rest of this step:
Save the config template:
kindo config init --template > config.yamlFill it in beside the Config reference. Replace each example value with your own, and delete the optional settings you don’t use, such as the secret store and model access settings if they don’t apply. Keep the file out of version control: once it’s filled in, it holds credentials.
Fill in your routing. With Kindo-managed ingress, uncomment the ingress section and set these:
| Config setting | Set it to |
|---|---|
className | Your ingress controller’s IngressClass, such as nginx, alb or kong. |
annotations | Annotations for every Ingress, such as load-balancer settings, or {}. With className: alb, set alb.ingress.kubernetes.io/group.name so every host shares one load balancer. |
externalDns | true to have external-dns publish your DNS records. |
tls.certManager.clusterIssuer | Your cert-manager cluster issuer. |
tls.secret.certificate, tls.secret.privateKey | Or your certificate, followed by any intermediates, and its unencrypted private key, both in PEM. |
tls.acm.certificateArn | Or, with className: alb, your AWS Certificate Manager certificate. |
Keep one TLS choice. If your load balancer or gateway serves its own certificate, delete the TLS section. For a full example for your controller, see Ingress, DNS, and TLS.
With your own routing, leave the ingress section commented out.
Save your config to the cluster:
kindo config init --file config.yamlIf it refuses because values in angle brackets are left, replace each one it lists with your own and run it again.
Delete your config template once it’s saved.
With Kindo-managed ingress, turn off response buffering for chat, or chat responses are cut short. Open the config:
kindo config editAdd the values for your controller. For ingress-nginx:
overrides: helmValues: api: ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-buffering: 'off' ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-read-timeout: '3600' ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-send-timeout: '3600'For Kong, in milliseconds:
overrides: helmValues: api: ingress.annotations.konghq\.com/read-timeout: '3600000' ingress.annotations.konghq\.com/write-timeout: '3600000'For any other controller, see Streaming chat responses.
Install Kindo
Section titled “Install Kindo”8. Install Kindo on the cluster
Section titled “8. Install Kindo on the cluster”Check your infrastructure first, if you want to:
kindo preflightInstall Kindo:
kindo installConfirm the test email to the superadmin arrived before you rely on sign-in codes. To skip it, run this instead:
kindo install --no-test-emailStore your superadmin key. It’s printed once, at the end of the output. Store it in your password manager. If you lose it, or it expires, sign in to the superadmin dashboard and create a new key under Keys > New key.
If a warning counts failed steps, run the command the output names.
If Flagsmith keeps crashing during its setup, its database usually rejects its password or can’t be reached. Fix that, then run the command again.
If installing stops partway, fix the cause and run the command again with the same CLI.
Check the result. Status should report Kindo installed and healthy, and the health check should report nothing critical.
kindo statuskindo doctorIf it doesn’t, run the command the output names.
9. Back up the config
Section titled “9. Back up the config”As soon as installing finishes, even with warnings, back it up. It asks for a passphrase. Store the backup apart from the passphrase.
kindo config backup --output kindo-$(date +%F).bundleFinish
Section titled “Finish”10. Move your feature flags to Flagsmith
Section titled “10. Move your feature flags to Flagsmith”Copy the flags:
kindo feature-flags migrateAnswer 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:
kindo config applyAnswer 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.
Next, set up access.
