A Flux controller for GitOps automation of OpenTofu and Terraform resources in Kubernetes.
Tofu Controller is a Kubernetes controller for Flux that enables GitOps automation for OpenTofu and Terraform resources. It allows teams to manage infrastructure and application resources declaratively, integrating infrastructure-as-code workflows with GitOps practices. The controller supports multiple models, from full automation to drift detection, providing flexibility in adoption.
Platform engineers, DevOps teams, and SREs managing Kubernetes clusters who want to apply GitOps principles to their OpenTofu or Terraform infrastructure. It's ideal for organizations using Flux for GitOps and seeking to extend it to infrastructure management.
Developers choose Tofu Controller because it seamlessly integrates Terraform/OpenTofu with Flux's GitOps capabilities, offering multiple operational models that allow incremental adoption. Its flexibility in handling existing infrastructure and drift detection makes it a practical tool for real-world infrastructure management.
A GitOps OpenTofu and Terraform controller for Flux
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers multiple operational models from full automation to drift detection, enabling teams to adopt GitOps incrementally without disrupting existing setups, as highlighted in the README's 'at your own pace' philosophy.
Built specifically for Flux, leveraging its GitOps engine to manage Terraform resources declaratively within Kubernetes, ensuring a consistent workflow for platform teams.
The Hybrid and State Enforcement models allow applying GitOps to parts of existing infrastructure, such as managing individual EKS components, making it practical for real-world environments.
Includes a dedicated model for monitoring infrastructure drift through GitOps, helping teams detect and respond to unauthorized changes proactively, as described in the feature list.
Requires a Kubernetes cluster and Flux setup, adding significant operational overhead and complexity for teams not already using this ecosystem, limiting its portability.
For small or static infrastructure with infrequent changes, the GitOps workflow and multiple models can introduce unnecessary complexity compared to direct Terraform execution.
Only supports Terraform and OpenTofu, excluding other popular IaC tools like Pulumi or CloudFormation, which may not suit diverse tooling environments.