terraform-provider-kubernetes
aws-virtual-gpu-device-plugin
Our great sponsors
terraform-provider-kubernetes | aws-virtual-gpu-device-plugin | |
---|---|---|
6 | 3 | |
1,541 | 132 | |
1.2% | - | |
9.0 | 0.0 | |
4 days ago | over 1 year ago | |
Go | Jupyter Notebook | |
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.
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.
aws-virtual-gpu-device-plugin
-
Share a GPU between pods on AWS EKS
This project (available here) uses the k8s device plugin described by this AWS blog post to make GPU-based nodes publish the amount of GPU resource they have available. Instead of the amount of VRAM available or some abstract metric, this plugin advertises the amount of pods/processes that can be connected to the GPU. This is controlled by what is called by NVIDIA as Multi-Process Service (MPS).
-
[D] Serverless solutions for GPU inference (if there's such a thing)
AWS has apparently already started using this type of tech as of this year (see lost below). They mention virtual gpus but this particular solution probably won't help OP unfortunately. https://aws.amazon.com/blogs/opensource/virtual-gpu-device-plugin-for-inference-workload-in-kubernetes/
-
AWS open source news and updates No.41
The post explores GPU device plugin to address how to set fractional number of GPU resource for each pod by implementing the Kubernetes device plugin and Nvidia MPS. This project has been open sourced on GitHub.
What are some alternatives?
azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl
kserve - Standardized Serverless ML Inference Platform on Kubernetes
terrajet - Generate Crossplane Providers from any Terraform Provider
aws-eks-share-gpu - How to share the same GPU between pods on AWS EKS
k8s-device-plugin - NVIDIA device plugin for Kubernetes
asdf-tflint - An asdf plugin for installing terraform-linters/tflint.
determined - Determined is an open-source machine learning platform that simplifies distributed training, hyperparameter tuning, experiment tracking, and resource management. Works with PyTorch and TensorFlow.
asdf-hashicorp - HashiCorp plugin for the asdf version manager
booster - Software development framework specialized in building highly scalable microservices with CQRS and Event-Sourcing. It uses the semantics of the code to build a fully working GraphQL API that supports real-time subscriptions.
terraform-provider-ovirt - Terraform provider for oVirt 4.x