helmsman
terraform-provider-flux
Our great sponsors
| helmsman | terraform-provider-flux | |
|---|---|---|
| 7 | 3 | |
| 1,350 | 330 | |
| 1.6% | 4.0% | |
| 8.5 | 9.0 | |
| 6 days ago | 4 days ago | |
| Go | Go | |
| MIT License | 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.
helmsman
-
Helm-Compose – The Docker-compose like tool for K8s development
We've been using Helmsman (https://github.com/Praqma/helmsman) for the same use case. It supports some other creature comforts (automatic fetching of parameters from AWS SSM, chart ordering, etc.) and seems a bit more mature.
-
Which GitOps for very small teams?
I've been using https://github.com/Praqma/helmsman for quite a few years now. Very pleased with it.
-
[2022] [Updated] Alternative to Helmfile
Have you looked at https://github.com/Praqma/helmsman ?
- Question on how to handle common infrastructure services;
-
How do you deliver Kubernetes applications in 2022?
Kustomize manifests. Each microservice in its own folder. We have around 10 microservices, so it works for us. Db/metrics/monitoring/operators go into a Helmsman file.
-
Terraform/helm and environment variables
I'm using Helmsman. It's a wrapper around Helm that allows you to inject environmental variables, amongst other things. It allows me to easily inject environmental variables from my Gitlab CI/CD into my Helm release.
-
How do you automate Helm charts installation?
Here's some issues where people asked the same question: https://github.com/Praqma/helmsman/issues/18 https://github.com/roboll/helmfile/issues/240
terraform-provider-flux
-
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?
helmfile - Deploy Kubernetes Helm Charts
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kube-linter - KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.
helm-mapkubeapis - This is a Helm plugin which map deprecated or removed Kubernetes APIs in a release to supported APIs
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
website - 🌐 Source code for OpenGitOps website
k2tf - Kubernetes YAML to Terraform HCL converter
helm-controller - The GitOps Toolkit Helm reconciler, for declarative Helming
kustomize-controller - The GitOps Toolkit Kustomize reconciler