task: update documentation for v26.1.2-rc.1

[nvidia-ci-cd]

Created by the docs-ci job in Mellanox/network-operator-docs.

[github-actions]

Documentation preview

https://mellanox.github.io/network-operator-docs/review/pr-388

[greptile-apps]

Greptile Summary

This is an automated documentation update for the v26.1.2-rc.1 release candidate, bumping all image versions and SHA-256 digests from v26.1.1 to v26.1.2-rc.1. Notably, every image registry reference has been changed from the production registries (nvcr.io/nvidia/cloud-native and nvcr.io/nvidia/mellanox) to the staging registry nvcr.io/nvstaging/mellanox.

• All 13 files (docs, Helm defaults, and processed example YAMLs) have version strings, SHA digests, and repository URLs updated consistently for the new RC.
• The DOCA-OFED driver image list gains several new multi-arch manifest tags (without explicit -amd64/-arm64 suffixes) and expands RHCOS and RHEL coverage.
• The doca-driver-version-lts variable changed from doca3.2.2-25.10-2.4.1.0-4 to 24.10-0.7.0.0-0, which drops the doca prefix and does not match the tag naming convention used elsewhere in the docs.

Confidence Score: 3/5

The RC documentation is internally consistent for the version bump, but the wholesale switch to the staging registry and the malformed LTS driver version string need review before this goes to a wider audience.

Two concrete defects exist: the doca-driver-version-lts variable was changed to a string (24.10-0.7.0.0-0) that doesn't follow the doca{version}-... convention used everywhere else and doesn't correspond to any tag visible in the SHA digest table. Additionally, all image repositories now point to nvcr.io/nvstaging/mellanox, a staging registry that is typically not publicly accessible.

docs/common/vars.rst is the most important file to verify — particularly the doca-driver-version-lts value and the wholesale switch to nvcr.io/nvstaging/mellanox for all repositories.

Important Files Changed

Filename	Overview
docs/common/vars.rst	Version bumped from v26.1.1 to v26.1.2-rc.1; all image repositories switched from nvcr.io/nvidia/* to nvcr.io/nvstaging/mellanox (staging); doca-driver-version-lts format changed from doca3.2.2-25.10-2.4.1.0-4 to 24.10-0.7.0.0-0, dropping the doca prefix, which is a suspicious inconsistency
docs/advanced/images-sha256.rst	All image digests updated to v26.1.2-rc.1; repositories switched to nvcr.io/nvstaging/mellanox; new multi-arch manifest tags (without explicit arch suffix) added for Ubuntu, RHEL, RHCOS, and SLES; RHCOS coverage expanded to include rhcos4.16 and rhcos4.19
docs/customizations/helm.rst	Default Helm chart values updated to reference nvcr.io/nvstaging/mellanox and version network-operator-v26.1.2-rc.1 across all sub-chart sections
examples/processed/host-device-rdma/10-nicclusterpolicy.yaml	Repository and version updated to nvstaging/mellanox and v26.1.2-rc.1 consistently across all image specs
examples/processed/ipoib-rdma-shared/complete.yaml	Repository and version updated to nvstaging/mellanox and v26.1.2-rc.1 for all component specs including doca-driver
examples/processed/sriov-ib-rdma/complete.yaml	Repository and version updated to nvstaging/mellanox and v26.1.2-rc.1 consistently
examples/processed/sriov-network-rdma/complete.yaml	Repository and version updated to nvstaging/mellanox and v26.1.2-rc.1 consistently

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Network Operator Docs v26.1.2-rc.1] --> B{Image Registry}
    B -->|All components| C[nvcr.io/nvstaging/mellanox]
    C --> D[network-operator:v26.1.2-rc.1]
    C --> E[doca-driver:doca3.3.0-26.01-1.0.0.0-4]
    C --> F[sriov-network-operator:network-operator-v26.1.2-rc.1]
    C --> G[k8s-rdma-shared-dev-plugin:network-operator-v26.1.2-rc.1]
    C --> H[multus-cni:network-operator-v26.1.2-rc.1]
    C --> I[...and 15+ other components]

    subgraph Previous Release v26.1.1
        J[nvcr.io/nvidia/cloud-native] --> K[network-operator:v26.1.1]
        L[nvcr.io/nvidia/mellanox] --> M[all other components:network-operator-v26.1.1]
    end

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Network Operator Docs v26.1.2-rc.1] --> B{Image Registry}
    B -->|All components| C[nvcr.io/nvstaging/mellanox]
    C --> D[network-operator:v26.1.2-rc.1]
    C --> E[doca-driver:doca3.3.0-26.01-1.0.0.0-4]
    C --> F[sriov-network-operator:network-operator-v26.1.2-rc.1]
    C --> G[k8s-rdma-shared-dev-plugin:network-operator-v26.1.2-rc.1]
    C --> H[multus-cni:network-operator-v26.1.2-rc.1]
    C --> I[...and 15+ other components]

    subgraph Previous Release v26.1.1
        J[nvcr.io/nvidia/cloud-native] --> K[network-operator:v26.1.1]
        L[nvcr.io/nvidia/mellanox] --> M[all other components:network-operator-v26.1.1]
    end

Loading

_{Reviews (1): Last reviewed commit: "task: update documentation for v26.1.2-r..." | Re-trigger Greptile}

[greptile-apps]

Staging registry used across all documentation

Every image repository in this PR has been switched from nvcr.io/nvidia/mellanox (or nvcr.io/nvidia/cloud-native) to nvcr.io/nvstaging/mellanox. The nvstaging registry is typically access-restricted and hosts pre-release artifacts — users following these docs or applying the example YAMLs verbatim will attempt to pull from a registry they may not have credentials for, resulting in ImagePullBackOff. This affects all 13 changed files.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

LTS driver version string format changed unexpectedly

The doca-driver-version-lts value changed from doca3.2.2-25.10-2.4.1.0-4 to 24.10-0.7.0.0-0. Every other driver version string in this PR follows the doca{doca_version}-{kernel_version}-... pattern (e.g. doca3.3.0-26.01-1.0.0.0-4), but the new LTS value drops the doca prefix entirely and does not match any tag format visible in images-sha256.rst. If this variable is used to construct an image reference, the tag 24.10-0.7.0.0-0 would not resolve, leaving LTS driver deployments broken.

Suggested change

	.. |doca-driver-version-lts| replace:: 24.10-0.7.0.0-0
	.. |doca-driver-version-lts| replace:: doca3.2.2-25.10-2.4.1.0-4