Kubernetes - Kuest Owner Docs

Prerequisites

Working Kubernetes cluster and context
Ingress controller available
Base values from Environment Variables
A storage profile from Manual Installation Overview

Baseline deploy

cp infra/kubernetes/secret.example.yaml infra/kubernetes/secret.yaml
kubectl apply -k infra/kubernetes

The baseline Kustomize resources do not run database migrations. Run pnpm db:push from a secured environment connected to the production database before routing traffic to a release.

Important configuration points

SITE_URL must match the canonical public URL.
In infra/kubernetes/secret.example.yaml, set exactly one storage profile:
- Supabase with SUPABASE_*
- S3 with S3_BUCKET, S3_ACCESS_KEY_ID, and S3_SECRET_ACCESS_KEY

Verify the rollout before updating public DNS:

kubectl -n kuest rollout status deployment/kuest-web
kubectl -n kuest get pods,service,ingress

Scheduler

If the supplied database jobs are not active, edit infra/kubernetes/cronjobs.yaml for your namespace, secret name, and SITE_URL, then apply it:

kubectl apply -f infra/kubernetes/cronjobs.yaml

The jobs should follow Scheduled Jobs.

Optional Terraform

cd infra/terraform/environments/production/kubernetes
cp terraform.tfvars.example terraform.tfvars
terraform init
terraform plan
terraform apply