[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]

Confidence Score: 3/5

[Medium impact] The version change reaches OFED driver selection in examples and release configuration.

Fix the webhook rejection and driver-check parser before merging.

Findings

1.  Webhook rejects the new version ▶
2.  Driver check selects wrong manifest ▶

Summary

Changes the driver version to doca3.3.4-26.01-2.0.0.0.719-0 in seven example policies and both driver entries in hack/release.yaml.

• Sample policies and release defaults now use OFED driver version doca3.3.4-26.01-2.0.0.0.719-0.

_{Reviews (1) · Last reviewed commit: "ci: update OFED version to doca3.3.4-26...." · Reviewed by Greptile}

[greptile-apps]

Webhook rejects the new version

With webhook validation enabled, all seven changed example policies are rejected on spec.ofedDriver.version. The DOCA pattern in isValidOFEDVersion accepts four dot-separated numbers before the final dash, but 2.0.0.0.719-0 has five.

Extend the validator to accept this format and add a test for the exact new version before switching the examples.

[greptile-apps]

Driver check selects wrong manifest

Changing Mofed.version to doca3.3.4-… breaks make check-doca-drivers. The prefix-removal pattern in Makefile:483 requires the DOCA patch number to be 0, so it leaves this version unchanged. The next split sets DRIVERVERSION to doca3.3.4 instead of 26.01, causing the target to request the wrong release manifest.

Update the parser to accept nonzero patch numbers, or use the second dash-separated field as the release workflow already does.