documents VS tofu-controller

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.

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.

The GitOps term was coined back in 2017 by Weaveworks, and paraphrasing OpenGitOps, a GitOps system is based on the following principles:

That's why there's systems for continuous reconciliation. I'ts one of the four fundamental principles of GitOps.

https://opengitops.dev/ https://github.com/open-gitops/documents

(Here is a link: https://github.com/open-gitops/documents/pull/51)

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.

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.

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.

https://github.com/weaveworks/tf-controller/issues/1166#issu...

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...

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.

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.

tf-controller which is integrated with Flux GitOps and reconciles Terraform files in a control loop

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.

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.

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.