Kubernetes support is currently in early access. To get on the list, book a demo call with the Tembo team: Book a Demo
github.existingSecret; leave that out to set up GitHub later. With their Helm values, the chart’s defaults run everything Tembo needs: the platform, Postgres and Redis, and a pool of agent hosts. To change any of it, see Configuration.
Don’t pass --wait to the first helm install with Helm 4. Its default wait strategy waits for the host pool, which becomes ready only after the chart’s post-install database migrations run, so the install times out. Later helm upgrade --wait runs are fine, since migrations run before the upgrade.
The chart is at oci://registry.tembo.io/tembo. Sign Helm in to the registry with your license key as the password:
On AWS
Createvalues.yaml:
tembo-aws.json from AWS prerequisites, first so yours override them:
kubectl -n tembo get ingress,svc shows them): your hostname for the Ingress, and postgres.<your-host> and redis.<your-host> for the tembo-postgresql-hosts and tembo-redis-hosts Services. Agent hosts reach the database and Redis at those names.
The first agent host is ready in about four minutes:
On GCP
Createvalues.yaml:
ingress.gke serves Tembo through GKE’s Ingress with a Google-managed certificate for your hostname, and redirects HTTP to HTTPS.
Install the chart with the module’s values, tembo-gcp.json from GCP prerequisites, first so yours override them:
kubectl -n tembo get ingress,svc shows them): your hostname for the Ingress, and postgres.<your-host> and redis.<your-host> for the tembo-postgresql-hosts and tembo-redis-hosts Services. The certificate is issued once your hostname resolves to the Ingress, which can take up to an hour.
The first agent host is ready in a few minutes:
On Azure
Coming soon.After installing
- Sign in. Open
https://<your-host>, sign up and create your workspace. - Add a model provider in Settings > Models. Sessions started from GitHub, and session titles, need an Anthropic API key or a workspace Claude subscription.
- Connect GitHub in Settings > Integrations (see Connect GitHub).
- Start a session on one of your repositories.
https://<your-host>/sign-up, then you invite them under Settings > Workspace > Members.
Troubleshooting
A host doesn’t reachReady. The controller replaces a host that doesn’t register within 15 minutes. Read its boot log with aws ec2 get-console-output --instance-id <instance-id> --latest and look for tembo-host-config. Hosts must reach the cluster’s API endpoint and the postgres. and redis. hostnames.
Connecting GitHub fails with “Failed to get extra data for integration”. The GitHub App needs the Members organization permission. Set it to Read-only, approve the change on your organization’s installation, then connect again.
GitHub says it sent an installation request. Only owners of the GitHub organization can connect it.
The agent can’t clone a repository. Enable it in Settings > Repositories.
Webhooks never arrive. Check the GitHub App’s Advanced > Recent deliveries. If GitHub can’t connect, your Ingress isn’t reachable from the internet. If deliveries succeed, check the app’s webhook secret against the one the install notes print.
Inviting a teammate fails with “Organization member not found”. They need to sign up first.
Sessions started from GitHub fail with “The gateway could not authenticate with its upstream provider”. Add an Anthropic API key or a workspace Claude subscription in Settings > Models.
Sessions fail at once, with “too many clients already” in the API’s logs. Postgres is out of connections. See Postgres and Redis.
A session fails with “Host CPU count (…) is too small” or “Host total memory (…) is too small”. Its size doesn’t fit your hosts’ instance type. See Instance types.