Update DRA example driver to v0.5.0

[harche]

Summary

Update the shared dra-example-driver-install step from v0.3.0 to v0.5.0.

v0.5.0 includes kubernetes-sigs/dra-example-driver#271. This updates the existing DRA example driver jobs for main, release-4.23, release-5.0, release-5.1, and release-5.2, including the openshift-priv variants.

Validation

• make registry-metadata
• YAML parsing and git diff --check

Summary by CodeRabbit

The shared dra-example-driver-install CI step now downloads dra-example-driver version v0.5.0 instead of v0.3.0. This affects DRA example driver jobs for OpenShift branches and openshift-priv variants.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 2385a3e4-df7f-43d0-bdbd-3221da05145d

📥 Commits

Reviewing files that changed from the base of the PR and between 9614a66 and 2352f9e.

📒 Files selected for processing (1)

• ci-operator/step-registry/dra-example-driver/install/dra-example-driver-install-ref.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

The install reference updates the default DRA_EXAMPLE_DRIVER_VERSION from v0.3.0 to v0.5.0.

Changes

DRA example driver version update

Layer / File(s)	Summary
Update default driver version ci-operator/step-registry/dra-example-driver/install/dra-example-driver-install-ref.yaml	The default DRA_EXAMPLE_DRIVER_VERSION changes from v0.3.0 to v0.5.0.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 2352f

This PR updates the shared DRA example driver version and has no identified merge-blocking impact.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the DRA example driver to version v0.5.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS. The pull request changes one YAML value: DRA_EXAMPLE_DRIVER_VERSION from v0.3.0 to v0.5.0. It adds no Ginkgo tests or test titles, and the affected step directory contains no It, `Descri…
Test Structure And Quality	✅ Passed	PASS. The pull request changes only one YAML step reference: the default DRA_EXAMPLE_DRIVER_VERSION changes from v0.3.0 to v0.5.0. It adds no Ginkgo test code or test operations, so the listed r…
Microshift Test Compatibility	✅ Passed	PASS: The pull request changes only the default DRA_EXAMPLE_DRIVER_VERSION from v0.3.0 to v0.5.0 in a YAML step reference. It adds no Ginkgo e2e tests or test names, and it introduces no direct …
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS. The pull request changes one YAML install-step reference only: DRA_EXAMPLE_DRIVER_VERSION changes from v0.3.0 to v0.5.0. The changed file contains no Ginkgo test declarations or test logic…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS. The PR changes only one step-registry field: DRA_EXAMPLE_DRIVER_VERSION from v0.3.0 to v0.5.0. It does not modify deployment manifests, operator code, controllers, node selectors, affiniti…
Ote Binary Stdout Contract	✅ Passed	PASS. The pull request changes only the YAML default for DRA_EXAMPLE_DRIVER_VERSION, from v0.3.0 to v0.5.0. It adds no OTE binary code or process-level setup such as main(), init(), `TestMai…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The pull request changes one YAML default from v0.3.0 to v0.5.0. It adds no Ginkgo tests and introduces no IPv4 assumptions or test connectivity requirements. The installer’s existing GitHub…
No-Weak-Crypto	✅ Passed	The pull request changes only the default driver version from v0.3.0 to v0.5.0. The installer logic is unchanged and contains no weak-crypto usage. The v0.5.0 source archive also contains no exact…
Container-Privileges	✅ Passed	The pull request changes only DRA_EXAMPLE_DRIVER_VERSION from v0.3.0 to v0.5.0. It adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation setting. …
No-Sensitive-Data-In-Logs	✅ Passed	PASS — The pull request changes only the default DRA_EXAMPLE_DRIVER_VERSION from public value v0.3.0 to v0.5.0. The changed value is not a password, token, API key, PII, session ID, internal hos…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@harche: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-origin-main-e2e-aws-ovn-dra-example	openshift/origin	presubmit	Registry content changed
pull-ci-openshift-origin-release-5.2-e2e-aws-ovn-dra-example	openshift/origin	presubmit	Registry content changed
pull-ci-openshift-origin-release-5.1-e2e-aws-ovn-dra-example	openshift/origin	presubmit	Registry content changed
pull-ci-openshift-origin-release-5.0-e2e-aws-ovn-dra-example	openshift/origin	presubmit	Registry content changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-dra-example	openshift/origin	presubmit	Registry content changed
pull-ci-openshift-kubernetes-master-k8s-e2e-aws-ovn-dra-serial	openshift/kubernetes	presubmit	Registry content changed
pull-ci-openshift-kubernetes-release-5.2-k8s-e2e-aws-ovn-dra-serial	openshift/kubernetes	presubmit	Registry content changed
pull-ci-openshift-kubernetes-release-5.1-k8s-e2e-aws-ovn-dra-serial	openshift/kubernetes	presubmit	Registry content changed
pull-ci-openshift-kubernetes-release-5.0-k8s-e2e-aws-ovn-dra-serial	openshift/kubernetes	presubmit	Registry content changed
pull-ci-openshift-kubernetes-release-4.23-k8s-e2e-aws-ovn-dra-serial	openshift/kubernetes	presubmit	Registry content changed
periodic-ci-openshift-kueue-operator-main-test-e2e-ci-build-upstream-dra-4-22	N/A	periodic	Registry content changed
periodic-ci-openshift-kueue-operator-release-1.4-test-e2e-ci-build-upstream-dra-4-22	N/A	periodic	Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[harche]

/pj-rehearse auto-ack

[PannagaRao]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, PannagaRao

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/dra-example-driver/install/OWNERS [PannagaRao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

@harche: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

[harche]

/pj-rehearse periodic-ci-openshift-kueue-operator-main-test-e2e-ci-build-upstream-dra-4-22

[harche]

/pj-rehearse pull-ci-openshift-origin-main-e2e-aws-ovn-dra-example

[harche]

/pj-rehearse pull-ci-openshift-kubernetes-master-k8s-e2e-aws-ovn-dra-serial

[harche]

/retest-required

[openshift-merge-bot]

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-merge-bot]

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-merge-bot]

@harche: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

[harche]

/pj-rehearse periodic-ci-openshift-kueue-operator-main-test-e2e-ci-build-upstream-dra-4-22

[openshift-merge-bot]

@harche: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@harche: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/agent-model-policy	2352f9e	link	true	/test agent-model-policy
ci/prow/core-valid	2352f9e	link	true	/test core-valid
ci/rehearse/openshift/origin/main/e2e-aws-ovn-dra-example	2352f9e	link	unknown	/pj-rehearse pull-ci-openshift-origin-main-e2e-aws-ovn-dra-example

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.