k2tf
terraform-provider-kubernetes
k2tf | terraform-provider-kubernetes | |
---|---|---|
4 | 6 | |
1,142 | 1,541 | |
- | 0.5% | |
2.7 | 9.0 | |
6 months ago | 5 days ago | |
Go | Go | |
Mozilla Public License 2.0 | Mozilla Public 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-kubernetes
-
Does the kubernetes provider behave differently than other provider?
Now, to be honest, I'm not entirely sure/confident how this works. When I've used this kind of setup, I had two separate workspaces: one for setting up EKS and one for setting up Kubernetes within EKS. I'd apply the EKS workspace, first, then use its outputs for the Kubernete's workspace. You can see this pattern is specifically outlined in this EKS/k8s example. The Kubernetes provider docs also explicitly warns against creating the cluster in the same module as the Kubernetes provider. So it appears this may work, but it isn't recommended.
-
Name for move from Terraform to Kubernetes Operators
It is a pretty important distinction. Terraform and Kubernetes are fundamentally different in how they work. If you ever try to manage kubernetes state from terraform, it the differences become very obvious: https://github.com/hashicorp/terraform-provider-kubernetes/issues/1367
-
terraform-kubernetes-provider how to create secret from file?
I'm using the terraform kubernetes-provider and I'd like to translate something like this kubectl command into TF:
-
Share a GPU between pods on AWS EKS
After the resources be provisioned, you might want to run terraform apply -refresh-only to refresh your local state as the creation of some resource change the state of others within AWS. Also, state differences on metadata.resource_version of k8s resources almost always show up after an apply. This seems to be related to this issue.
-
Kubernetes provider awfully trigger happy to delete entire state when it can't connect
You can open an issue here: https://github.com/hashicorp/terraform-provider-kubernetes/issues
-
What are your experiences in using the Kubernetes and Helm Providers?
We want to do that, but this issue has been a huge blocker for us. You might not hit it unless you’re using AKS, though.
What are some alternatives?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl
hcl - HCL is the HashiCorp configuration language.
terrajet - Generate Crossplane Providers from any Terraform Provider
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
k8s-device-plugin - NVIDIA device plugin for Kubernetes
terraform-provider-flux - Terraform and OpenTofu provider for bootstrapping Flux
asdf-tflint - An asdf plugin for installing terraform-linters/tflint.
asdf-awscli
asdf-hashicorp - HashiCorp plugin for the asdf version manager