k2tf
kapp
k2tf | kapp | |
---|---|---|
4 | 7 | |
1,142 | 860 | |
- | 0.6% | |
2.7 | 8.5 | |
6 months ago | 2 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)
kapp
- HELM vs KUSTOMIZE
-
How to handle the lifecycle of multiple COTS
If you want to take it one step further: you might be applying several resources at a time that are logically one "application". kapp (https://carvel.dev/kapp/) lets you group those together and give them a name, and provides a "terraform-like" experience where it shows you its execution plan before applying updates. So then you might do `ytt -f | kapp deploy -a name-of-thing` Or you could use helm's templating engine but then still pass the resulting yaml to kapp for its unification of the deployment step.
-
Dhall: A Gateway Drug to Haskell
since you mentioned Kubernetes...
> It would be nice if there was a separate state reconciliation system that one could adapt to use with Cue or Dhall or any other frontend
this exactly was thinking behind https://carvel.dev/kapp for Kubernetes (i'm one of the maintainers). it makes a point to not know how you decided to generate your Kubernetes config -- just takes it as input.
> In particular the ability to import other files as semantic hashes seems like a great feature.
it's an interesting feature but seems like it should be unnecessary given that config can be easily checked into git (your own and its dependencies).
-
Terraform should have remained stateless
i think kubernetes is not a great example in favor of more client state (like tf) since k8s has uniform resource structure (metadata.*) and first class labeling support. but as you point out kubectl doesnt use labels well (at least imho).
when building https://carvel.dev/kapp (which i think of as "optimized terraform" for k8s) the goal was absolutely to take advantage of those k8s features. we ended up providing two capabilities: direct label (more advanced) and "app name" (more user friendly). from impl standpoint, difference is how much state is maintained.
"kapp deploy -a label:x=y -f ..." allows user to specify label that is applied to all deployed resources and is also used for querying k8s to determine whats out there under given label. invocation is completely stateless since burden of keeping/providing state (in this case the label x=y) is shifted to the user. downside of course is that all apis within k8s need to be iterated over. (side note, fun features like "kapp delete -a label:!x" are free thanks to k8s querying).
"kapp deploy -a my-app -f ..." gives user ability to associate name with uniquely auto-generated label. this case is more stateful than previous but again only label needs to be saved (we use ConfigMap to store that label). if this state is lost, one has to only recover generated label.
imho k8s api structure enables focused tools like kapp to be much much simpler than more generic tool like terraform. as much as i'd like for terraform to keep less state, i totally appreciate its needs to support lowest common denominator feature set.
common discussion topics:
-
Is there any CLI tool to sync between local yamls and current cluster namespace state?
Take a look at kapp (https://github.com/vmware-tanzu/carvel-kapp).
-
Deploy Neo4J's APOC plugin with code thanks to CARVEL vendir
kapp - Install, upgrade, and delete multiple Kubernetes resources as one "application"
-
Open Application Model – An open standard for defining cloud native apps
I really like this approach for simplifying Kubernetes. A few projects similar to OAM in that it provides a higher level "Application" CRD:
https://github.com/vmware-tanzu/carvel-kapp
What are some alternatives?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
kubevela - The Modern Application Platform.
hcl - HCL is the HashiCorp configuration language.
argo-cd - Declarative Continuous Deployment for Kubernetes
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
Flux - Successor: https://github.com/fluxcd/flux2
terraform-provider-flux - Terraform and OpenTofu provider for bootstrapping Flux
kapp-controller - Continuous delivery and package management for Kubernetes.
terraform-provider-kubernetes - Terraform Kubernetes provider
ytt - YAML templating tool that works on YAML structure instead of text
asdf-awscli
carvel - Carvel provides a set of reliable, single-purpose, composable tools that aid in your application building, configuration, and deployment to Kubernetes. This repo contains information regarding the Carvel open-source community.