aws-eks-share-gpu
containers-roadmap
| aws-eks-share-gpu | containers-roadmap | |
|---|---|---|
| 1 | 80 | |
| 8 | 5,146 | |
| - | 0.4% | |
| 0.0 | 2.0 | |
| almost 2 years ago | 9 months ago | |
| HCL | Shell | |
| - | GNU General Public License v3.0 or later |
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
-
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).
containers-roadmap
-
General Availability of the AWS SDK for Rust
Thanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh — Part 1
Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane · Issue #1792 · aws/containers-roadmap
-
Running a Web Application with 100% AWS Fargate Spot Containers 🤘
As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :
-
Kubernetes SidecarContainers feature is merged
Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.
If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else
https://github.com/aws/containers-roadmap/issues/696
- AWS Config supports recording exclusions by resource type
- Announcing pull through cache for registry.k8s.io in Amazon Elastic Container Registry
-
EKS/Spot vs EKS Fargate/Spot?
Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622
- audit logging of the master plane in EKS
-
How to use Podman inside of a container
Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626
- How to keep 100% availability with a single ec2 spot instance?
What are some alternatives?
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
eks-nvme-ssd-provisioner - EKS NVMe SSD provisioner for Amazon EC2 Instance Stores
k8s-device-plugin - NVIDIA device plugin for Kubernetes
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
terraform-provider-kubernetes - Terraform Kubernetes provider
netshoot - a Docker + Kubernetes network trouble-shooting swiss-army container
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.
kraken - P2P Docker registry capable of distributing TBs of data in seconds
k2tf - Kubernetes YAML to Terraform HCL converter
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
asdf-hashicorp - HashiCorp plugin for the asdf version manager
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.