[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: 4/5

[Medium impact] The change reaches OFED release defaults and example cluster policies.

Fix the policy validator before merging; it rejects the new driver version in every updated example.

Findings

1.  Updated policies are rejected ▶
2.  Driver check selects wrong file ▶

Summary

Changes the DOCA driver version from doca3.6.0-26.10-059000-0 to doca3.3.1-26.01-2.0.0.0.506-0.

• OFED release defaults and example policies use the new driver version.

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

[greptile-apps]

Updated policies are rejected

With policy validation enabled, the webhook rejects this version in all seven updated examples. isValidOFEDVersion accepts four dot-separated build numbers before the final hyphen, but 2.0.0.0.506-0 has five. Kubernetes therefore rejects spec.ofedDriver.version before the operator can deploy the driver. Extend the validator to accept this format and add a regression test alongside the version bump.

[greptile-apps]

Driver check selects wrong file

The new doca3.3.1 prefix breaks version extraction in make check-doca-drivers. The expression at Makefile:483 only strips prefixes ending in .0-, so DRIVERVERSION becomes doca3.3.1 rather than 26.01. Developers running the check now request release_manifests/doca3.3.1.yaml instead of the intended release_manifests/26.01.yaml. Update the extraction to support nonzero patch versions alongside this bump.