k2tf
terraform-provider-flux
k2tf | terraform-provider-flux | |
---|---|---|
4 | 3 | |
1,142 | 330 | |
- | 3.6% | |
2.7 | 9.0 | |
6 months ago | 10 days ago | |
Go | Go | |
Mozilla Public 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.
k2tf
-
Tool to convert set of yaml ( kustomize generated ) to terraform ?
This might be what you are looking for: https://github.com/sl1pm4t/k2tf
-
HELM vs KUSTOMIZE
... and if you're an opinionated person, like me, and you value consolidated infrastructure atomicity as a whole along side locks for everything. You'd port cherry-picked helm charts as terraform modules with k2tf, and build every docker container from scratch, with forced layer invalidation to perform security updates for every image, using the docker and kubernetes providers respectively.
-
Share a GPU between pods on AWS EKS
Pro tip: If you want to convert k8s yaml files to .tf, you can use k2tf (repo) that is able to convert the resource types of the yaml top their appropriated counterparts of the k8s provider for terraform. To install it, just:
-
Does anyone use terraform to manage Kubernetes objects as opposed to using plain yamls/helm charts/kustomize?
Almost all is created as manifest/helm in K8S world, too much toil to convert (tool like https://github.com/sl1pm4t/k2tf help but exists corners cases)
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?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
hcl - HCL is the HashiCorp configuration language.
helmfile - Deploy Kubernetes Helm Charts
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
terraform-provider-kubernetes - Terraform Kubernetes provider
helmsman - Helm Charts as Code
asdf-awscli
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
k8s-device-plugin - NVIDIA device plugin for Kubernetes
kustomize-controller - The GitOps Toolkit Kustomize reconciler