terraform-provider-docker VS tofu-controller

... and if you're an opinionated person, like me, and you value consolidated infrastructure atomicity as a whole along side locks for everything. You'd port cherry-picked helm charts as terraform modules with k2tf, and build every docker container from scratch, with forced layer invalidation to perform security updates for every image, using the docker and kubernetes providers respectively.

For the docker management, we are going to use terraform module kreuzwerker/docker. It provides us an opportunity to build and upload docker image to a docker repository.

Communication is crucial; that's why we want to keep it public, even if we receive private requests through other channels such as @gophers/terraform-provider-docker in Slack. We encourage engineers to open an issue or use the recently released discussions feature from GitHub. The code of conduct helped us set the etiquette guidelines, how we want to work together, and which tone and politeness we expect.

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.