aws-eks-share-gpu
How to share the same GPU between pods on AWS EKS (by DanielKneipp)
k8s-device-plugin
NVIDIA device plugin for Kubernetes (by NVIDIA)
| aws-eks-share-gpu | k8s-device-plugin | |
|---|---|---|
| 1 | 11 | |
| 8 | 2,411 | |
| - | 3.7% | |
| 0.0 | 9.6 | |
| almost 2 years ago | 5 days ago | |
| HCL | Go | |
| - | 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.
aws-eks-share-gpu
Posts with mentions or reviews of aws-eks-share-gpu.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-04.
-
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).
k8s-device-plugin
Posts with mentions or reviews of k8s-device-plugin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-09.
-
Unlocking AI and ML Metal Performance with QBO Kubernetes Engine (QKE) Post
https://github.com/NVIDIA/k8s-device-plugin/issues/332#issue...
- Nos – Open-Source to Maximize GPU Utilization in Kubernetes
- Show HN: Nos – Open-Source to Maximize GPU Utilization in Kubernetes
-
Time-Slicing GPUs with Karpenter
K8s-device-plugin
-
Understanding Kubernetes Limits and Requests
This framework allows the use of external devices (e.g., NVIDIA GPUs, AMD GPUS, SR-IOV NICs) without modifying core Kubernetes components.
-
Nvidia GPU Plugin: Am I really limited to one pod per GPU?
Not talking about MIG. NVIDIA device plugin. https://github.com/NVIDIA/k8s-device-plugin
- Nvidia Kubernetes plugin install option that does not require Helm?
-
What is the difference between nvidia device plugin and GPU operator?
GPU Operator Device plugin
-
Share a GPU between pods on AWS EKS
If you ever tried to use GPU-based instances with AWS ECS, or on EKS using the default Nvidia plugin, you would know that it's not possible to make a task/pod shared the same GPU on an instance. If you want to add more replicas to your service (for redundancy or load balancing), you would need one GPU for each replica.
-
Looking for a sanity check on a project I'm working on at home, hoping you fine people can help - Raspberry Pi Kubernetes Cluster
Some notes on Plex/Emby/Kodi and transcoding. If you want true transcoding with GPU acceleration, you have to have Nvidia GPU or be a k8s device plugin genius. The whole idea of mounting elastic devices in k8s is fairly new and rather complex. In the mean time transcoding is best done on a beefy device with a proper CPU (eg i7) or specifically Nvidia GPU because there are numerous pre-made plugins. I just run Plex and Emby on an old ATX gaming machine without GPU acceleration and it works totally fine. They were barely usable for just me when running on the RPis, wouldn't recommend it unless you can figure out how to mount the correct devices in the pod using a custom raspberry pi device plugin . . . lol good luck! - Arm labs device manager: https://community.arm.com/developer/research/b/articles/posts/a-smarter-device-manager-for-kubernetes-on-the-edge - Deis labs Akri device manager: https://github.com/deislabs/akri - Nvidia GPU plugin: https://github.com/NVIDIA/k8s-device-plugin
What are some alternatives?
When comparing aws-eks-share-gpu and k8s-device-plugin you can also consider the following projects:
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
kubevirt-gpu-device-plugin - NVIDIA k8s device plugin for Kubevirt
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
harvester - Open source hyperconverged infrastructure (HCI) software
terraform-provider-kubernetes - Terraform Kubernetes provider
aws-ami-gpu-monitoring - This project contains the code necessary to build an AWS AMI with monitoring capabilities of GPU usage (among other metrics) using CloudWatch.
k2tf - Kubernetes YAML to Terraform HCL converter
asdf-hashicorp - HashiCorp plugin for the asdf version manager
asdf-awscli
aws-eks-share-gpu vs aws-virtual-gpu-device-plugin
k8s-device-plugin vs kubevirt-gpu-device-plugin
aws-eks-share-gpu vs containers-roadmap
k8s-device-plugin vs harvester
aws-eks-share-gpu vs terraform-provider-kubernetes
k8s-device-plugin vs aws-virtual-gpu-device-plugin
aws-eks-share-gpu vs aws-ami-gpu-monitoring
k8s-device-plugin vs terraform-provider-kubernetes
aws-eks-share-gpu vs k2tf
k8s-device-plugin vs containers-roadmap
aws-eks-share-gpu vs asdf-hashicorp
k8s-device-plugin vs asdf-awscli