ci: update OFED version to doca3.2.3-25.10-3.0.9.0-0

[nvidia-ci-cd]

Created by an internal DOCA CI job.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Summary

This automated PR (from an internal DOCA CI job) updates the OFED/DOCA driver version across all example NicClusterPolicy CRs and hack/release.yaml. However, the change is a version downgrade from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0 — two DOCA major point releases older — which may not be intended for the master branch.

• All seven example CR YAMLs have their ofedDriver.version changed from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
• hack/release.yaml updates both Mofed and MofedStigFips entries to the same downgraded version.
• All files still reference the nvcr.io/nvstaging/mellanox staging registry, consistent with CI usage.

Confidence Score: 4/5

The change is a uniform DOCA driver version replacement across example CRs and the release manifest, but it moves to an older DOCA version (3.2.3) from a newer one (3.4.0), which warrants confirmation that this is the intended target for the master branch.

All eight files receive an identical single-line version string change generated by an automated CI job. The downgrade from DOCA 3.4.0 to 3.2.3 across every example CR and the release manifest could be intentional (e.g., targeting a different release train), but it is an unusual direction for an automated update on master and should be explicitly confirmed before merging.

hack/release.yaml is the most authoritative version source; confirm the intended DOCA version there first, as all CRs derive from it.

Important Files Changed

Filename	Overview
hack/release.yaml	Downgrades Mofed and MofedStigFips DOCA driver version from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0 — a major version regression from 3.4 to 3.2.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full-ocp.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-ipoib.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-nvidia-ipam.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-ocp-hostdev.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-ocp.yaml	ofedDriver version downgraded from doca3.4.0-26.04-0.8.6.0-0 to doca3.2.3-25.10-3.0.9.0-0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Internal DOCA CI Job] -->|triggers PR| B[Version Update]
    B --> C[hack/release.yaml]
    B --> D[example/crs/*.yaml x7]
    C --> E[Mofed: doca3.4.0 → doca3.2.3]
    C --> F[MofedStigFips: doca3.4.0 → doca3.2.3]
    D --> G[ofedDriver.version: doca3.4.0 → doca3.2.3]
    E & F & G --> H[nvcr.io/nvstaging/mellanox/doca-driver:doca3.2.3-25.10-3.0.9.0-0]

Loading

_{Reviews (1): Last reviewed commit: "ci: update OFED version to doca3.2.3-25...." | Re-trigger Greptile}

[greptile-apps]

Version downgrade from DOCA 3.4.0 to 3.2.3

This PR replaces doca3.4.0-26.04-0.8.6.0-0 with doca3.2.3-25.10-3.0.9.0-0 — a regression across two major DOCA point releases (3.4 → 3.2). The same downgrade is applied to both Mofed and MofedStigFips entries here, as well as all seven example CRs. If this is intentional (e.g., targeting a specific stable/LTS DOCA branch for a release), please confirm that doca3.2.3 is the correct target for the master branch rather than a staging or release-candidate branch.

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!