skypilot-org/skypilot

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

Open

#9,035 建立於 2026年3月10日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Python (4,859 star) (311 fork)batch import
good first issuegood starter issues

描述

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.

貢獻者指南

技術棧
pythonkubernetes
領域
backendinfrastructurecloud
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Pythonbasic Kubernetes GPU concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Locate the function ` accelerator name matches()` in the SkyPilot codebase that performs prefix based fuzzy matching for GPU names on Kubernetes. The function currently accepts any name where the actual GPU name (e.g., H100) is a prefix. Modify it to filter against the set of GPU variants actually available on the cluster, as reported by `sky show gpus infra k8s`. Consider using exact matching or look up the available variants before deciding whether a requested GPU variant is valid.