flamingo
terranetes-controller
| flamingo | terranetes-controller | |
|---|---|---|
| 7 | 4 | |
| 582 | 110 | |
| 3.6% | 6.4% | |
| 8.5 | 9.6 | |
| about 2 months ago | 4 days ago | |
| Go | Go | |
| Apache License 2.0 | GNU General Public License v3.0 only |
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
terranetes-controller
-
Options for handling Terraform with ArgoCD
Terranetes might be another option
- Self-Service Of Cloud Resources - Terraform Controller
-
Terraform Controller for Kubernetes - Enable controlled self service of cloud resources
Hey u/skarlso! Apologies about the cookie settings, that was a bug but should be fixed shortly, thanks for reporting it. Looking at the tf-controller it's missing a few features which is in the appvia/terraform-controller project: - There's no built-in admission control to restrict where users can source modules from (cluster operators would need to leverage OPA Gatekeeper etc and write their own policies). - The terraform runs are executed in a Pod in the user's own namespace, so cloud access can be exposed directly to those users (rather than only the cluster operators). - No predicted cloud cost support - No support for global variables The native flux support is nice but you could still follow a GitOps approach with this too, creating a helm chart leveraging tf2helm and a HelmRepository resource.
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.
cfnctl - Cfnctl brings the Terraform cli experience to AWS Cloudformation :cloud:
Echo - High performance, minimalist Go web framework
Selefra - The open-source policy-as-code software that provides analysis for Multi-Cloud and SaaS environments, you can get insight with natural language (powered by OpenAI).
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
Vault - A tool for secrets management, encryption as a service, and privileged access management
Buffalo - Rapid Web Development w/ Go
provider-terraform - A @crossplane provider for Terraform
weave-gitops - Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.
Cloud-Native-Guide - Cloud Native Guide
httprouter - A high performance HTTP request router that scales well
Fiber - ⚡️ Express inspired web framework written in Go