Skip to content

docs(npu-operator): rewrite install page for OperatorHub flow + add release notes#792

Open
luohua13 wants to merge 1 commit into
release-4.3from
docs/npu-operator-1.2-form-update-release-4.3
Open

docs(npu-operator): rewrite install page for OperatorHub flow + add release notes#792
luohua13 wants to merge 1 commit into
release-4.3from
docs/npu-operator-1.2-form-update-release-4.3

Conversation

@luohua13
Copy link
Copy Markdown
Contributor

Backport of #790 to release-4.3.

Summary

The 1.2.0 release of Alauda Build of NPU Operator changes the delivery model from cluster plugin (Marketplace > Cluster Plugins) to OLM operator (Marketplace > OperatorHub). This PR adapts the NPU Operator installation page to match and adds a release notes page that mirrors the per-product layout used by hami-docs.

  • Installation page rewritten to split the flow into:
    • Downloading / uploading both the operator package and cluster plugin packages.
    • Installing the Node Feature Discovery / Volcano cluster plugins from Marketplace > Cluster Plugins.
    • Installing the NPU Operator from Marketplace > OperatorHub (Install dialog, namespace selector, deployment form).
    • Verification updated to use the OperatorHub details page and watch the npu-driver pod in the operator namespace.
    • Obsolete manual ServiceMonitor snippet removed — the operator now ships npu-exporter-servicemonitor in its own namespace.
    • Form table: Driver Version row exposed as a top-level input (default 25.5.0); volcano components intentionally absent.
  • Release notes added for v1.2.0 (openFuyao npu-operator 1.2.0) and v1.1.3 (openFuyao npu-operator 1.1.1). Headlines: cluster-plugin-to-operator delivery change (no in-place upgrade from v1.1.3), MindCluster/Ascend v7.3.0 stack bump, npu-exporter ServiceMonitor fix.

Test plan

  • Render the page locally; confirm the install steps and release notes display correctly.
  • Cross-check the deployment form table against a 1.2.0 OperatorHub install on a 4.3 cluster.
  • Verify the auto-installed npu-exporter-servicemonitor is present with the documented kubectl command.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (3)
  • main
  • master
  • ^\d.x$

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1a5635de-bc63-4f6f-b546-8e4cab6c7f0e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/npu-operator-1.2-form-update-release-4.3

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

…elease notes

The 1.2.0 release of Alauda Build of NPU Operator changes the delivery
model from cluster plugin (`Marketplace > Cluster Plugins`) to OLM
operator (`Marketplace > OperatorHub`). Adapt the installation page
and add a release notes page mirroring the per-product layout used
by hami-docs.

Installation page:
- Rename Downloading/Uploading sections from "Cluster plugin" to
  "Packages" and enumerate both the operator package (npu-operator)
  and the cluster plugin packages (NFD required, Volcano optional).
- Split installation into two subsections: NFD as a Cluster Plugin
  and NPU Operator via OperatorHub (Install dialog, namespace
  selector, deployment form).
- Bump default Driver Version to 25.5.0 and rename the row to match
  the form label; add a note that all operator-managed pods land in
  the operator namespace and that Volcano components are absent.
- Verification step 1 switches from the Cluster plugin page to the
  OperatorHub details page / Installed Operators view.
- Verification step 2 watches the npu-driver pod in the operator
  namespace (was kube-system) with a note for non-default namespaces.
- Installing Monitor: drop the obsolete manual ServiceMonitor snippet
  (which targeted the wrong namespaces); the operator now auto-
  installs npu-exporter-servicemonitor in its own namespace.

Release notes:
- v1.2.0 mapped to openFuyao npu-operator 1.2.0; headline is the
  cluster-plugin-to-operator delivery change (no in-place upgrade
  from v1.1.3) and the MindCluster/Ascend v7.3.0 stack bump.
- Downstream bug fix highlighted is the npu-exporter ServiceMonitor
  not taking effect; plus the two community 1.1.1 -> 1.2.0 fixes.
- v1.1.3 mapped to openFuyao npu-operator 1.1.1 (MindCluster v7.2.RC1,
  cluster-plugin delivery).
@JounQin JounQin force-pushed the docs/npu-operator-1.2-form-update-release-4.3 branch from 1e1685b to 609f7bc Compare May 14, 2026 11:07
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying alauda-container-platform with  Cloudflare Pages  Cloudflare Pages

Latest commit: 609f7bc
Status: ✅  Deploy successful!
Preview URL: https://10c61af2.alauda-container-platform.pages.dev
Branch Preview URL: https://docs-npu-operator-1-2-form-u.alauda-container-platform.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant