terraform-provider-flux
Terraform provider for bootstrapping Flux (by fluxcd)
source-controller
The GitOps Toolkit source management component (by fluxcd)
Our great sponsors
terraform-provider-flux | source-controller | |
---|---|---|
3 | 1 | |
328 | 223 | |
4.0% | 0.5% | |
8.3 | 9.2 | |
6 days ago | 1 day ago | |
Go | Go | |
Apache License 2.0 | 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.
terraform-provider-flux
Posts with mentions or reviews of terraform-provider-flux.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-09.
-
Using Terraform to both create kubernetes clusters (AKS) and deploy helm charts in the same project - good or bad?
IMO, a better approach would be to provision your cluster using terraform, then do cluster operations using a GitOps tool, such as GitOps Toolkit (Flux v2) - https://toolkit.fluxcd.io/. You can point multiple clusters to the same repo and they are going to apply and reconcile the desired state for all or your clusters if needed. There’s also a Flux terraform provider - https://github.com/fluxcd/terraform-provider-flux, bootstrap flux then let it do its job.
- Does anyone use terraform to manage Kubernetes objects as opposed to using plain yamls/helm charts/kustomize?
-
How do you automate Helm charts installation?
You could try this: https://github.com/fluxcd/terraform-provider-flux
source-controller
Posts with mentions or reviews of source-controller.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-12.
-
Deploy with Kustomize, FluxCD and Remote Resources
There is some follow-up improvements to come, like OCI registries (announced in FluxCD 0.32), to replace flux.GitRepository. We still need this issue to be solved to be able to use it with all features provided by Kustomize.
What are some alternatives?
When comparing terraform-provider-flux and source-controller you can also consider the following projects:
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kustomize-controller - The GitOps Toolkit Kustomize reconciler
helmfile - Deploy Kubernetes Helm Charts
podinfo - Go microservice template for Kubernetes
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
helmsman - Helm Charts as Code
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
k2tf - Kubernetes YAML to Terraform HCL converter
helm-controller - The GitOps Toolkit Helm reconciler, for declarative Helming
terraform-provider-flux vs flux2
source-controller vs kustomize-controller
terraform-provider-flux vs helmfile
source-controller vs podinfo
terraform-provider-flux vs terraform-aws-eks
source-controller vs flux2
terraform-provider-flux vs helmsman
terraform-provider-flux vs helm-operator
terraform-provider-flux vs k2tf
terraform-provider-flux vs kustomize-controller
terraform-provider-flux vs helm-controller