Versions and Components

This page lists the maintained NPU Operator versions and the product components users need to consider during installation, upgrade, and support.

Current version

ComponentProduct versionDelivery modelUpstream baseline
Alauda Build of NPU Operatorv26.6.0OperatorHub / OLM operatoropenFuyao npu-operator 26.6.0

Current delivery characteristics

AreaCurrent value
Driver lifecyclePre-installed Host driver, managed Host installation, or managed precompiled Driver image
Runtime integrationascend RuntimeClass backed by ascend-docker-runtime; admission webhook injection is enabled by default
Precompiled Driver imageSelected automatically from the Driver version, node chip label, and complete kernel release label; imported separately from the product package
Containerized Driver image examplesARM64 alaudadockerhub/ascend-driver:25.5.0-310p-6.6.0-0008.ctl4 for CTyunOS-based Alauda OS 310P and alaudadockerhub/ascend-driver:25.5.0-910b-6.6.0-145.0.4.135-oe2403sp3 for openEuler 910B; see Install NPU Operator and use an exact node-profile match
Node discoveryAlauda Build of Node Feature Discovery is a prerequisite; NPU Feature Discovery maintains component placement labels and adds Ascend-specific labels

Historical delivery model

VersionDelivery modelNotes
v1.2.4OperatorHub / OLM operatorPrevious Stable release based on openFuyao npu-operator 1.2.0.
v1.1.3Cluster PluginOlder delivery model based on openFuyao npu-operator 1.1.1 and the MindCluster / Ascend v7.2.RC1 component stack.

v26.6.0 component stack

ComponentVersionDefaultUser-visible purpose
NPU Operator, Webhook, and Managerv26.6.0EnabledReconciles NPUOperatorCtl, admission, and managed NPU components.
NPU Driver Installerv26.6.0-1Enabled for managed Host installationInstalls the Host driver on supported mutable operating systems.
Ascend Runtimev7.3.0-1EnabledProvides the ascend-docker-runtime payload used by the containerd ascend runtime handler.
NPU Container Toolkit26.6.0EnabledInstalls and maintains the containerd ascend runtime handler configuration.
NPU Feature Discovery26.6.0EnabledMaintains component placement labels and adds Ascend-specific labels as discovery data becomes available.
NPU Node Provision26.6.0Used by optional MindIO componentsProvisions the optional MindIO TFT or MindIO ACP components.
Ascend Device Plugin, Operator, NodeD, ClusterD, and NPU Exporterv7.3.0Component-dependentProvides device exposure, training, resilience dependencies, and monitoring.
Resilience Controllerv7.1.RC1DisabledOptional recovery controller for validated deployments.

The precompiled Driver image used on immutable operating systems is not included in the product package. Import the ARM64 image that matches the target node profile and map its complete source reference to the target workload cluster registry.

Supported architecture and hardware

ArchitectureHardwareNotes
ARMAscend 910BSupported by v26.6.0.
ARMAscend 310PSupported by v26.6.0.

ACP integration points

IntegrationValue
ACP versionsv4.0-v4.3
Operator namespacenpu-operator by default; managed operands also use kube-system, npu-exporter, monitoring, mindx-dl, and default according to the component
Main custom resourceNPUOperatorCtl
Resource keysConfirm from node allocatable resources. Common examples include huawei.com/Ascend910 for 910-family devices, huawei.com/Ascend310P, and other environment-specific huawei.com/Ascend* keys.
Runtime integrationruntimeClassName: ascend, injected automatically for Ascend resource requests when the admission webhook is enabled
Quota metadataConfigured in ACP through CustomResourceLimitation metadata
MonitoringNPU Exporter; ServiceMonitor when the monitoring namespace exists; dashboard managed in ACP
External prerequisiteAlauda Build of Node Feature Discovery installed on the target workload cluster

Do not treat this page as an upstream hardware matrix. Only list combinations that are delivered or supported by Alauda Build of NPU Operator.