Tofu Controller (previously known as Weave TF-Controller) is a controller for Flux to reconcile OpenTofu and Terraform resources in the GitOps way. With the power of Flux together with OpenTofu and Terraform, Tofu Controller allows you to GitOps-ify infrastructure, and application resources, in the Kubernetes and IAC universe, at your own pace.
"At your own pace" means you don't need to GitOps-ify everything at once.
Tofu Controller offers many GitOps models:
- GitOps Automation Model: GitOps your OpenTofu and Terraform resources from the provision steps to the enforcement steps, like a whole EKS cluster.
- Hybrid GitOps Automation Model: GitOps parts of your existing infrastructure resources. For example, you have an existing EKS cluster. You can choose to GitOps only its nodegroup, or its security group.
- State Enforcement Model: You have a TFSTATE file, and you'd like to use GitOps enforce it, without changing anything else.
- Drift Detection Model: You have a TFSTATE file, and you'd like to use GitOps just for drift detection, so you can decide to do things later when a drift occurs.
If you have a feature request to share or a bug to report, please file an issue. You can also reach out via our Tofu Controller Slack channel — get there by first joining the Weave Community Slack space.
To get started check out this guide on how to GitOps your Terraform resources with Tofu Controller and Flux.
Check out the documentation and use cases.
- Write back and show plan in PRs (Atlantis-like experience)
- CLI to GitOpsify existing Terraform workflows (UX improvement for CLI)
- Type safety for custom backends
- Improvement GitOps dependency management
- External drift detector
- Cloud cost estimation
- Observability - logging from the different stages of the runner
-
v1alpha3API - ARM64 & Gravitron support
-
v1beta1API (stabilization)
-
v1beta2API