Repository navigation
docs: verify vGPU pod annotations after config update #255
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -63,6 +63,11 @@ Or apply the plain manifest: | |
| kubectl apply -f deployments/static/volcano-vgpu-device-plugin.yml | ||
| ``` | ||
|
|
||
| After updating `volcano-scheduler-configmap`, `volcano-scheduler` hot-reloads | ||
| `volcano-scheduler.conf` once kubelet syncs the ConfigMap (typically within | ||
| about a minute), so restarting Volcano components is not required. Wait for the | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Restart the scheduler after enabling vGPU. In Volcano v1.15.0, if
|
||
| reload before creating vGPU workloads. | ||
|
|
||
| Useful chart options: | ||
|
|
||
| - `--set cdi.enabled=true` passes devices through CDI instead of environment variables. | ||
|
|
@@ -76,6 +81,19 @@ kubectl get node <node> -o jsonpath='{.status.allocatable}' | |
|
|
||
| `volcano.sh/vgpu-number` and `volcano.sh/vgpu-memory` should be listed. The number is the GPU count times `deviceSplitCount` (10 by default). | ||
|
|
||
| After creating a vGPU pod, verify that Volcano added the device allocation | ||
| annotations: | ||
|
|
||
| ```shell | ||
| kubectl get pod <pod> -o yaml | grep -E \ | ||
| 'volcano.sh/(devices-to-allocate|vgpu-ids-new|vgpu-node)' | ||
| ``` | ||
|
|
||
| If a pod was created before the updated configuration took effect and lacks | ||
| these annotations, kubelet may reject it with `UnexpectedAdmissionError: | ||
| Allocate failed due to rpc error: code = Unknown desc = cannot get valid pod`; | ||
| recreate the pod after the reload completes. | ||
|
|
||
| ## Run a vGPU job | ||
|
|
||
| Request vGPUs in `resources.limits`: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this note under the scheduler configmap yaml block