// the find
kbst/terraform-kubestack
Kubestack is a framework for Kubernetes platform engineering teams to define the entire cloud native stack in one Terraform code base and continuously evolve the platform safely through GitOps.
Kubestack is a Terraform framework that wraps EKS, AKS, GKE, and Scaleway clusters with a consistent module interface and bakes in a GitOps workflow using workspace-per-environment conventions. It's aimed at platform teams who want a single codebase managing clusters across clouds without writing all the Terraform boilerplate themselves. The Kustomize integration for deploying platform services on top of the cluster is the interesting design choice here.
The multi-environment workspace pattern (ops/apps per environment) is a real convention rather than a suggestion — it actually constrains how you structure your state, which is more useful than a blank-slate module. The companion Kustomization provider (kbst/terraform-provider-kustomization) means you can manage Kubernetes manifests through Terraform without shelling out to kubectl, keeping the apply graph coherent. The quickstart scaffolding via the `kbst` CLI generates valid, working code that you can read and modify immediately rather than dumping you into a black-box abstraction. Tests exist and are written as `.tftest.hcl` files using native Terraform test support, not a separate Python harness.
712 stars after what appears to be several years of development is a warning sign — the GitOps-via-Terraform niche is contested (Atlantis, Spacelift, env0) and Kubestack hasn't broken through. The last push was March 2026 but the contributor graph is thin; this is effectively a one-organization project and if kbst stops maintaining it, you own the Terraform. The Kustomize-inside-Terraform approach forces you to apply Kubernetes changes through Terraform's plan/apply cycle, which is slower and more fragile than Flux or ArgoCD for anything that changes frequently. There's no mention of Helm support, so teams with Helm-heavy platforms have to work around the framework rather than with it.