kyma-project / kyma-project/gpu

GPU capacity and allocation in status

Open
#69 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2
Forks
3
PR merge metrics
No merged PRs in 30d

Description

todo after time-slicing feature is added

kubectl get gpu shows total GPUs, how many in use, across which namespaces

Before
NAME READY REASON DRIVER VERSION NODES READY AGE
gpu True Ready 590 1 5m

After (with time-slicing, shipped together)
NAME READY REASON DRIVER VERSION NODES READY TOTAL GPUs ALLOCATED AGE
gpu True Ready 590 3 12 8 5m

TOTAL GPUs
Read from node labels that NVIDIA sets automatically after driver installation - nvidia.com/gpu.count per node, summed across all GPU nodes. We don't set this, we read it. When time-slicing is active NVIDIA advertises virtual GPUs instead of physical ones, so this number already reflects the sharing configuration. No user action needed.

ALLOCATED
Computed by listing all running pods across all namespaces and summing nvidia.com/gpu resource requests. A pod requesting nvidia.com/gpu: 2 contributes 2 to the count. We don't set this either - we derive it from the cluster state on every reconcile. Reflects current demand, not capacity.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the kubectl get gpu status entry point and the reconcile path that reads node labels and running pods across namespaces. Implement the TOTAL GPUs and ALLOCATED values shown in the requested output, including time-slicing values, and verify that allocation sums nvidia.com/gpu requests while the status remains accurate on each reconcile.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.