kustomize-controller
The GitOps Toolkit Kustomize reconciler (by fluxcd)
terraform-provider-flux
Terraform and OpenTofu provider for bootstrapping Flux (by fluxcd)
| kustomize-controller | terraform-provider-flux | |
|---|---|---|
| 1 | 3 | |
| 246 | 332 | |
| 2.4% | 4.2% | |
| 9.0 | 9.0 | |
| 2 days ago | 5 days 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.
kustomize-controller
Posts with mentions or reviews of kustomize-controller.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Why Helm never felt like it belonged
The combination of the tools I mention at the end would likely satisfy all of your needs. kustomize-controller, which is the part of flux that deploys your application, has the ability to check if the deployment's health check failed. I assume it also has the ability to rollback (or at least it easily might in the future). it also tracks the state of the applied objects so that it can delete objects that are not used anymore.
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
What are some alternatives?
When comparing kustomize-controller and terraform-provider-flux you can also consider the following projects:
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
helm-controller - The GitOps Toolkit Helm reconciler, for declarative Helming
helmfile - Deploy Kubernetes Helm Charts
source-controller - The GitOps Toolkit source management component
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
kustomize-controller vs flux2
terraform-provider-flux vs flux2
kustomize-controller vs helm-controller
terraform-provider-flux vs helmfile
kustomize-controller vs source-controller
terraform-provider-flux vs terraform-aws-eks
terraform-provider-flux vs helmsman
terraform-provider-flux vs helm-operator
terraform-provider-flux vs k2tf
terraform-provider-flux vs helm-controller
terraform-provider-flux vs source-controller