documents
๐ Lasting documents from the GitOps Working Group which are versioned and released together (including the GitOps Principles and Glossary) (by open-gitops)
tofu-controller
A GitOps OpenTofu and Terraform controller for Flux (by flux-iac)
Our great sponsors
documents | tofu-controller | |
---|---|---|
10 | 14 | |
385 | 1,149 | |
2.6% | 10.4% | |
5.3 | 9.6 | |
about 1 month ago | 11 days ago | |
Go | ||
GNU General Public License v3.0 or later | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
documents
Posts with mentions or reviews of documents.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-17.
-
Introducing Digger v4.0 - An Open Source GitOps tool for Terraform that runs within your existing CI system.
It's not about terraform handling it or not, it's about ensuring that drift is automatically corrected without a CI trigger. One of the core principles of GitOps is continuous reconciliation. This requires a reconciliation loop, e.g. some task that runs automatically and without user intervention. As far as I can tell from their docs Digger only runs its steps on a pull request, similar to Atlantis (but "without the backend"). This is continuous delivery, but it's not continuous reconciliation, and therefore not GitOps. GitOps would be something like combining Flux or ArgoCD with Crossplane.
-
hey gitops community: we have a multicluster terminology question for you
think i'm going to take the feedback from this discussion to the opengitops working group tomorrow, hoping we can maybe get it defined in their vendor agnostic gitops glossary https://github.com/open-gitops/documents/blob/main/GLOSSARY.md haha, which i'm sure chatgpt will figure out about like 12 seconds later, consider correct, and then just wire the architecture together for us. but we can just start with kubefirst while chatgpt is trying to catch up haha.
-
How to apply security at the source using GitOps
The GitOps term was coined back in 2017 by Weaveworks, and paraphrasing OpenGitOps, a GitOps system is based on the following principles:
-
Drawbacks of CICD
That's why there's systems for continuous reconciliation. I'ts one of the four fundamental principles of GitOps.
-
AWS EKS Setup with eksctl & Argo CD installation, configuration & deploy app with ArgoCD & Kustomize
https://opengitops.dev/ https://github.com/open-gitops/documents
-
Question for declarative GitOps managed shops
(Here is a link: https://github.com/open-gitops/documents/pull/51)
-
GitOps in a nutshell
In 2021, the first OpenGitOps Standard v1 was created, to make sure we all GitOps enthusiasts speak the same language. For more information go to opengitops.dev.
- OpenGitOps Documents v1.0.0-rc.1 is a pre-release for feedback from the wider community. ยท open-gitops/documents
- open-gitops/documents
-
Open GitOPs Principles v0.1.0 Pre-release is now available!
The working group has been hard at work, over many meetings, github discussions, revisions, blood, sweat, and tears we've just merged the pre-release GitOps Principles and glossary. Check them out here and be sure to make issues/comments. It'd be great to hear everyone's thoughts.
tofu-controller
Posts with mentions or reviews of tofu-controller.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-12.
-
Self-service infrastructure as code
We stumbled upon a project for maintaining Terraform with CRDs that we could deploy with Helm. That project is now called Tofu-Controller - another WeaveWorks project, so it integrated great with our existing Flux setup.
-
Weaveworks Seems to Be Disintegrating
https://github.com/weaveworks/tf-controller/issues/1166#issu...
-
Disaster Recovery for AWS EKS Infra
Weave's TF-Controller, which also has fewer bugs, much better adoption, and it looks like it's actually being developed by someone. But requires a weird argocd <-> flux interop boilerplate. It's a "controller for flux" and not a Kubernetes controller, and I don't really get such ambiguous targeting , but meh...
-
Migrate from terragrunt to terraform
Wrt tools, I wanted to integrate terraform with Flux thanks to their tf-controller. Conciling the core gitops features with terraform would be great imho.
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
I'm using Flux instead of Argo which has support for running terraform from a given Git Repo or OCI artifact so essentially I still fall back on Terraform when needed and it's applied via GitOps.
- Looking for teammate to join project (not a job posting)
-
MySQL operators without the cluster
tf-controller which is integrated with Flux GitOps and reconciles Terraform files in a control loop
-
Automate your Terraform using GitOps with Flux
While searching for alternatives for running Terraform using Kubernetes, I found several controllers and operators, but none that I felt had as much potential as the tf-controller from Weaveworks. We are already using Flux as our GitOps tool, and the tf-controller works by utilizing some of the core functionality from Flux, and has a custom resource for Terraform deployments. The source controller takes care of fetching our modules, the kustomize controllers apply the Terraform resources, and then the controller spin up static pods (called runners) that runs your Terraform commands.
-
2022 was a great year for GitOps
For us, GitOps is a vital part of how we operate, and it is the magic sauce that fuels our platform offering. Not only do we use it for application deployments, but by utilizing the Weaveworks tf-controller, we can create services using Terraform to automate our infrastructure deployments.
-
Terraform to deploy and KEDA to scale - will it work?
Some further research brought me to Weaveworks' TF-Controller which appears to be able to do what I want at least for the initial deployment step. Flux CD (also by Weaveworks) integrates with KEDA now, so it would be great if it could also integrate with KEDA to manage terraform-deployed Azure resources.
What are some alternatives?
When comparing documents and tofu-controller you can also consider the following projects:
website - ๐ Source code for OpenGitOps website
crossplane - The Cloud Native Control Plane
argocd-tooling-applications
atlantis - Terraform Pull Request Automation
bootstrap-repo
helm-operator - Successor: https://github.com/fluxcd/helm-controller โ The Flux Helm Operator, once upon a time a solution for declarative Helming.
drawio-architecture-diagrams
jsonnet-controller - A fluxcd controller for managing manifests declared in jsonnet
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
documents vs website
tofu-controller vs crossplane
documents vs argocd-tooling-applications
tofu-controller vs atlantis
documents vs bootstrap-repo
tofu-controller vs helm-operator
documents vs drawio-architecture-diagrams
tofu-controller vs jsonnet-controller
documents vs flux2
tofu-controller vs flux2
tofu-controller vs bootstrap-repo
tofu-controller vs flux2