Choose your path
Every option below installs the same product from the same Helm chart — nothing here is a different product or a stripped-down edition. What changes is the installer (Terraform applies it directly, or ArgoCD reconciles it as GitOps) and the target it lands on (a single k3s node, GKE, or EKS). Finish Prerequisites once, then pick the combination below that matches your cluster.
Credentials, Postgres, hostname, network access, and tooling — needed on every path.
PrerequisitesThe simplest deployment — one Linux node, in-cluster Postgres + Redis by default.
single-node k3sReuse an existing GKE cluster, or let Terraform provision a private one in the same apply.
GKE (Google Cloud)Reuse an existing EKS cluster, or let Terraform provision one, backed by RDS Postgres.
EKS (AWS)A cloud-agnostic alternative to terraform apply — reconcile the same chart via GitOps.
How the required pull-through image cache works — and doesn’t — on each target.
Registry optionsPostgres and Redis posture — bundled vs. external — compared across every target.
Datastore options