Alauda Container Platform

Release Notes

TOC

v1.2.0Breaking changesNew featuresBug fixesv1.1.3

v1.2.0

Based on the openFuyao npu-operator 1.2.0 community release.

Breaking changes

  • Delivery model changed from cluster plugin to operator. Earlier versions of Alauda Build of NPU Operator shipped as a cluster plugin, installed from Marketplace > Cluster Plugins. Starting with v1.2.0 the project is packaged as an OLM operator bundle and installed from Marketplace > OperatorHub.

    WARNING

    In-place upgrade from v1.1.3 (or any earlier cluster-plugin release) is not supported. To move to v1.2.0, uninstall the old cluster plugin first and then install the new operator from scratch:

    1. Uninstall the existing Alauda Build of NPU Operator cluster plugin from Marketplace > Cluster Plugins.
    2. If the driver is no longer needed on the host, run on each NPU node: 
      /usr/local/Ascend/driver/script/uninstall.sh
    3. Install v1.2.0 from Marketplace > OperatorHub following the Installation page.

New features

  • MindCluster / Ascend component stack upgraded to v7.3.0. Picks up the v7.3.0 train of ascend-docker-runtime, ascend-operator, ascend-k8sdeviceplugin, noded, vc-controller-manager, vc-scheduler, clusterd, and npu-exporter. The driver and firmware default version is bumped to 25.5.0.

Bug fixes

  • Fixed npu-exporter ServiceMonitor not taking effect: it was created in the wrong namespace and missed Prometheus selector labels, so the platform's Prometheus never scraped the exporter. The operator now ships a ServiceMonitor in its own namespace with the correct prometheus: kube-prometheus label and honorLabels: true.
  • (Community) Fixed installation / detection logic on nodes that do not have NPU cards.
  • (Community) Fixed environment-variable indicators not being deduplicated.

v1.1.3

Based on the openFuyao npu-operator 1.1.1 community release. Backed by the MindCluster / Ascend v7.2.RC1 component stack and delivered as a cluster plugin.