terraform-provider-flux
helm-operator
Our great sponsors
terraform-provider-flux | helm-operator | |
---|---|---|
3 | 5 | |
328 | 657 | |
4.0% | - | |
8.3 | 6.4 | |
6 days ago | over 1 year 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.
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
helm-operator
- Question for declarative GitOps managed shops
-
Auto helm (software) installations in ci/cd pipeline
You can store the values file of the helm in your repository and deploy with CI, but I personally prefer going to GitOps and Helm Operator (https://github.com/fluxcd/helm-operator) Or you can have a mixed approach where you define your HelmRelease to be deployed for HelmOperator and deploy it with CI (instead of having an operator in the cluster to apply every change in the repo)
-
Kubernetes State Checker
Nothing prevents you from making an operator that creates Deployment/Services/Ingress for you.
This is even simplified with Helm (to template your resources) and the HelmOperator[1].
[1] - https://github.com/fluxcd/helm-operator
-
How do you automate Helm charts installation?
I think you should check out flux and flux helm operator. https://github.com/fluxcd/helm-operator/stargazers
-
Gopher Gold #14 - Wed Oct 07 2020
fluxcd/helm-operator (Go): The Flux Helm Operator, for declarative Helming
What are some alternatives?
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kubebuilder - Kubebuilder - SDK for building Kubernetes APIs using CRDs
helmfile - Deploy Kubernetes Helm Charts
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
Flux - Successor: https://github.com/fluxcd/flux2
helmsman - Helm Charts as Code
spark-operator - Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes.
k2tf - Kubernetes YAML to Terraform HCL converter
Ory Kratos - Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!
kustomize-controller - The GitOps Toolkit Kustomize reconciler
tofu-controller - A GitOps OpenTofu and Terraform controller for Flux