Alauda Container Platform

Ascend

The Ascend vendor integration covers Huawei Ascend NPU enablement in ACP clusters, including NPU Operator, driver lifecycle, runtime integration, CDI, direct NPU allocation, and vendor-specific monitoring components when they are delivered in the target release.

TOC

Choose an Ascend pathRelated ACP pagesProduct documentationRelated concepts

Choose an Ascend path

NPU Operator manages the Ascend NPU software stack and can expose NPU resources to Kubernetes workloads through the vendor-standard path. Use the NPU product documentation for installation, driver lifecycle, upgrade, compatibility, release notes, and troubleshooting.

If a deployment uses NPU Operator only to prepare the Ascend base and uses HAMi Ascend Device Plugin to expose resources, use the HAMi product documentation for device exposure, resource requests, sharing semantics, and troubleshooting.

  • Use ACP accelerator pages to understand where Ascend fits in GPU/NPU capability navigation.
  • Use ACP quota pages for project and namespace quota operations.
  • Use ACP observability pages for dashboard and alert operations.
  • Use NPU product documentation for version-specific Ascend base behavior.
  • Use HAMi documentation for HAMi on Ascend NPU or HAMi on Ascend vNPU behavior.

Product documentation

Use the NPU product site for installation, driver lifecycle, compatibility, release notes, and troubleshooting.

Note
Because Alauda Ascend NPU releases on a different cadence from Alauda Container Platform, the Alauda Ascend NPU documentation is now available as a separate documentation set at Alauda Ascend NPU.