skypilot-org/skypilot

[Kubernetes] GPU prefix matching should not allow non-existent GPU variants

Open

#9,035 opened on Mar 10, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (311 forks)batch import
good first issuegood starter issues

Repository metrics

Stars
 (4,859 stars)
PR merge metrics
 (Avg merge 2d 23h) (146 merged PRs in 30d)

Description

On a K8s cluster where sky show-gpus --infra k8s shows only H100:

  • sky launch --gpus H100-MEGA succeeds (should it?)
  • sky launch --gpus 'NVIDIA:40GB+' shows H100-NVLINK, H100-SXM, H100-MEGA, H100-NVL as separate options, all resolving to the same physical H100

K8s prefix-based fuzzy matching in _accelerator_name_matches() accepts any name where H100 is a prefix (e.g., H100-MEGA, H100-SXM). The optimizer should filter against what's actually available on the cluster.

Contributor guide

Research direction
Examine the ` accelerator name matches()` function and the optimizer logic to filter available GPU variants based on cluster inventory.
Tech stack
pythonkubernetes
Domain
backendinfrastructuredevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesGPU concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75