Kubernetes support is currently in early access. To get on the list, book a demo call with the Tembo team: Book a Demo
- Cloud resources: on AWS or GCP, prepare your cluster and network, then apply Tembo’s Terraform module. It creates the cloud resources Tembo needs, and outputs the Helm values that use them.
- GitHub: create your install’s GitHub App, and keep its credentials in a Kubernetes Secret.
- Deploy: one
helm installwith the module’s Helm values and your own.
What you need
From Tembo, once you’re in early access:- A license key. It signs you in to Tembo’s registry,
registry.tembo.io, for the Helm chart and images, and gives your install the agent host image. - The chart version to install: 0.1.20 or later, the first on
registry.tembo.io. - The image tags for the platform and the host controller.
- A Kubernetes cluster with an Ingress controller, and a TLS certificate for your hostname. Your cloud’s page lists what the cluster needs.
- DNS for your hostname, through external-dns or records you create.
- Helm 3.8 or later, for charts from OCI registries, kubectl, and Terraform 1.5 or later.
What the module creates
Agent hosts run outside your cluster, as cloud instances the host controller launches. On each cloud, the module creates:- The host controller’s identity: a role bound to the chart’s service account, which can launch agent hosts and change or delete only its own.
- The agent hosts’ identity and network access: the role or service account hosts run as, and their firewall rules or security group.
- Object storage: a bucket for project images, session snapshots and file uploads, and the control plane’s access to it.
- Helm values for the chart: the identities above, a host class and pool named
default, and the bucket.
Choose your cloud
AWS
EKS, with agent hosts on EC2.
GCP
GKE, with agent hosts on Compute Engine.