Prepare Driver Images and ImageWhiteList
Use this page only when the selected installation scenario requires detailed Driver image import or ImageWhiteList preparation. Most users can start from Install NPU Operator, choose a scenario, and return here only when the scenario asks for these steps.
TOC
Select the matching precompiled Driver imageConfigure ImageWhiteListPhysical host and external Driver scenariosSelect the matching precompiled Driver image
For the immutable OS scenario, import the ARM64 Driver image that matches the complete (HDK, chip, kernel, OS) profile. NPU Operator derives the tag from the HDK version, detected chip, and complete kernel release after removing the architecture suffix:
For published openEuler tags, the legacy .oe separator in the kernel release becomes -oe. Do not add an OS suffix that is not present in the detected kernel release.
Example profiles:
Verify the source image architecture and mirror it to the target workload cluster registry:
If no published tag matches the node kernel, record uname -r and the chip model before contacting support.
Configure ImageWhiteList
If the target cluster enforces image whitelist policies, allow the exact Driver image reference rendered by NPU Operator and rewrite it to the image imported into the workload registry.
Apply the whitelist in the target workload cluster, preserve unrelated entries, and use one exact rule per supported Driver tag.
After creating the NPUOperatorCtl, verify the rendered reference and the image actually running:
The admitted image and its imageID must match the intended imported Driver artifact.
Physical host and external Driver scenarios
For an operator-managed physical host, use the delivered Driver installer and installMode: host, usePrecompiled: false. For an external Driver scenario, skip Driver image preparation and confirm that /usr/local/Ascend/driver is already healthy on every selected NPU node.