flamingo
tofu-controller
flamingo | tofu-controller | |
---|---|---|
7 | 14 | |
582 | 1,154 | |
3.6% | 3.3% | |
8.5 | 9.6 | |
about 2 months ago | 2 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
flamingo
-
Options for handling Terraform with ArgoCD
I'm aware of: - A k8s cronjob shelling out to the terraform CLI - flamingo -> Flux -> weaveworks Terraform controller - Terraform cloud operator - Crossplane's terraform provider
-
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...
- Argocd and Flux at the same time?
- What tool suggestions do you have for someone who's gonna set up an on-premise k8 cluster? Which tools do you use?
- GitHub - flux-subsystem-argo/flamingo: Flux Subsystem for Argo - Landing Repository
- ArgoCD vs. crossplane-helm provider for managing helm releases?
- chanwit/flamingo
tofu-controller
-
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?
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
crossplane - The Cloud Native Control Plane
Echo - High performance, minimalist Go web framework
atlantis - Terraform Pull Request Automation
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
Buffalo - Rapid Web Development w/ Go
jsonnet-controller - A fluxcd controller for managing manifests declared in jsonnet
weave-gitops - Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.
documents - 📑 Lasting documents from the GitOps Working Group which are versioned and released together (including the GitOps Principles and Glossary)
httprouter - A high performance HTTP request router that scales well
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.