Skip to content

fix: update HAMi-DRA version reference to v0.2.0 #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hami-robot merged 1 commit into from
Jun 23, 2026
Merged

fix: update HAMi-DRA version reference to v0.2.0 #486

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core-concepts/gpu-virtualization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ DRA is Kubernetes' next-generation solution for this, promoted to GA in v1.34. I

The scheduler can directly read device attributes from `ResourceSlice` for scheduling decisions. DRA also natively supports multiple Pods sharing the same device and cross-container device topology alignment.

HAMi currently remains based on Device Plugin, but the official team has launched the [HAMi-DRA](https://github.com/Project-HAMi/HAMi-DRA) subproject (v0.1.0, requires Kubernetes 1.34+), which converts HAMi's GPU resource requests into DRA `ResourceClaim` via MutatingWebhook, serving as a transitional solution for migrating to DRA.
HAMi currently remains based on Device Plugin, but the official team has launched the [HAMi-DRA](https://github.com/Project-HAMi/HAMi-DRA) subproject (v0.2.0, requires Kubernetes 1.34+), which converts HAMi's GPU resource requests into DRA `ResourceClaim` via MutatingWebhook, serving as a transitional solution for migrating to DRA.

## HAMi Virtual GPU Scheduling Principles

Expand Down
Loading