tfk8s
A tool for converting Kubernetes YAML manifests to Terraform HCL (by jrhouston)
terraform-kubernetes-manifests
Terraform modules for managing Kubernetes manifests (by e91e63)
tfk8s | terraform-kubernetes-manifests | |
---|---|---|
1 | 2 | |
924 | 0 | |
- | - | |
1.0 | 0.0 | |
4 months ago | about 2 years ago | |
Go | HCL | |
MIT License | 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.
tfk8s
Posts with mentions or reviews of tfk8s.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-23.
-
Is it normal to get by Terraform's Local Exec?
You can use tfk8s to autogenerate hcl from k8s yaml. It's not a random project, it's by a Hashicorp employee, one of the maintainers of the k8s provider.
terraform-kubernetes-manifests
Posts with mentions or reviews of terraform-kubernetes-manifests.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-23.
-
Is it normal to get by Terraform's Local Exec?
tfk8s definitely needs some manual finagling. I like to use it to translate small hand managed yaml from an example into tf. I'm not a fan of helm, but where it's the only option I'll use the helm provider. And when I get a large multi-document yaml file as the release artifact, I'll use the kubectl provider but the charts have to be split out and namespace deployed first - here's an example.
-
Is using an argocd provider for terraform an anti-pattern? Why not just use helm provider?
I've made a repo with terraform modules that handle all of these that fits my needs - https://github.com/e91e63/terraform-kubernetes-manifests/tree/main/modules
What are some alternatives?
When comparing tfk8s and terraform-kubernetes-manifests you can also consider the following projects:
k2tf - Kubernetes YAML to Terraform HCL converter
terraform-provider-argocd - Terraform provider for ArgoCD
amazon-cloudwatch-container-insights - CloudWatch Agent Dockerfile and K8s YAML templates for CloudWatch Container Insights.
lingon - Lingon is a collection of libraries and tools for building platforms using Go.
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
jk - Configuration as Code with ECMAScript