What the chart creates
Withingress.host: tembo.example.com:
- The internal Services carry their DNS name in an
external-dns.kubernetes.io/hostnameannotation. - The Postgres and Redis Services exist only with the bundled data stores and
compute.mode: controller. - Previews are on by default from chart 0.6.0, with Tembo releases later than 0.2.892. To turn them off, set
sandbar.enabled: false.
What you set up
1. An Ingress controller
It turns both Ingresses into load balancers, so users and webhooks can reach Tembo. Setingress.className and any ingress.annotations your controller needs. The previews’ Ingress gets the same ones.
For cloud-specific Ingress settings, follow AWS prerequisites or GCP prerequisites. With another controller, configure its annotations and TLS Secrets directly.
2. DNS
Every name in the table must resolve to its load balancer: browsers find Tembo by name, and agent hosts find Sandbar, Postgres and Redis by name.- With external-dns: it reads the Ingresses’ hosts and the Services’ annotations and creates the records.
- Without it: create the records yourself once the load balancers exist (
kubectl -n tembo get ingress,svc).
DNS for internal services
Use private DNS forpostgres.<your-host>, redis.<your-host> and sandbar.<your-host>. They only need to resolve from the VPC where agent hosts run. Prefer external-dns to maintain these records from the chart’s Service annotations, instead of copying load balancer addresses by hand. See AWS DNS or GCP DNS for the provider setup.
Keep the public app and preview records in your public DNS provider. If you use external-dns, configure its public and private zone filters so the internal Service records go only to private zones. Check name resolution from the hosts’ VPC before starting sessions.
Internal load balancers are still billed while hosts are scaled to zero. Include their forwarding rules, the public Ingresses, cluster nodes, storage and NAT in your idle-cost estimate; rates depend on the region and network setup.
3. TLS certificates
Tembo is served over HTTPS, so you need two certificates:tembo.example.com*.previews.tembo.example.com. A*.example.comcertificate doesn’t cover it.
ingress.public, you also need a certificate for its hostname. Cloud-managed certificates are covered in the provider prerequisites linked above.
If your Ingress controller uses Kubernetes TLS Secrets, cert-manager can issue them:
- Name the app’s Secret in
ingress.tls.secretName. The previews’ Secret istembo-previews-tlsby default; override it withingress.previews.tlsSecretName. - With
ingress.public, name its Secret iningress.public.tlsSecretName. - Add a
cert-manager.io/cluster-issuerannotation toingress.annotations. - Wildcards need a ClusterIssuer that uses DNS-01.