Request NPU Resources
After Alauda Build of NPU Operator is installed, workloads request Ascend NPUs through Kubernetes extended resource names.
This page covers direct whole-card allocation through Alauda Build of NPU Operator. If you have not selected the allocation owner, use Choose an Ascend NPU Allocation Mode first. For HAMi scheduling, sharing, virtualization, vNPU behavior, or HAMi-specific resource keys on Ascend devices, follow the HAMi path linked from that page.
Resource keys
The resource key must match what the device plugin reports in node allocatable resources. Do not derive the key only from the chip product name. For example, an Ascend 910B node may still report huawei.com/Ascend910.
Workload example
With the default admission webhook enabled, requesting the NPU resource is
enough in the submitted manifest. The webhook adds runtimeClassName: ascend
before the Pod is created, and the corresponding runtime handler injects the
device and Driver files. The workload image still provides CANN and the
application framework.
If the webhook is disabled, set runtimeClassName: ascend explicitly.
For example, if the node reports huawei.com/Ascend310P, use:
Quota fields in ACP
If the node reports the resource but ACP quota pages do not show it, configure accelerator resource metadata in ACP. See Accelerator Resource Quota.
RuntimeClass behavior
After creating a workload, inspect the admitted Pod:
The result should be ascend. A manifest that already sets this RuntimeClass remains valid; the webhook leaves an explicitly configured value unchanged.