[BUILD-2062] Update CSI driver image labels to el10

[adchauha]

Update Dockerfile CPE and image name labels.

Summary by CodeRabbit

• Chores
  • Updated container image metadata to reflect the latest OS compatibility target.
  • Applied the new metadata to both shared resource images; no runtime behavior changed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: adchauha
Once this PR has been reviewed and has the lgtm label, please assign adambkaplan for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 33a66ca9-74e6-4ab4-9dad-c5acbab6d13a

📥 Commits

Reviewing files that changed from the base of the PR and between b2f07f2 and f5eb350.

📒 Files selected for processing (2)

• .konflux/shared-resource-webhook/Dockerfile
• .konflux/shared-resource/Dockerfile

---

Walkthrough

The cpe label value in the LABEL metadata block was updated from the EL9-specific identifier to the EL10-specific identifier in two Konflux Dockerfiles: shared-resource-webhook/Dockerfile and shared-resource/Dockerfile.

Changes

Dockerfile CPE Label Updates

Layer / File(s)	Summary
Update cpe labels in Dockerfiles .konflux/shared-resource-webhook/Dockerfile, .konflux/shared-resource/Dockerfile	Changed the cpe value in the LABEL metadata block from an el9-specific identifier to an el10-specific identifier in both files.

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

🚥 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 matches the main change: updating image labels to el10.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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	Only two Dockerfiles changed; no test files or Ginkgo titles were modified, so the check is not applicable.
Test Structure And Quality	✅ Passed	The PR only changes two Dockerfile CPE labels; no Ginkgo test code or test-related logic was modified.
Microshift Test Compatibility	✅ Passed	Diff only changes two Dockerfiles; no Ginkgo tests or MicroShift-unsafe APIs/features were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only two Dockerfiles changed; no new/modified Ginkgo e2e tests or SNO-sensitive test code were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only two Konflux Dockerfiles changed, both label-only CPE updates; no manifests, controllers, or scheduling logic were modified.
Ote Binary Stdout Contract	✅ Passed	PR only changes two Dockerfile CPE labels; no process-level stdout code or init/main/suite setup was modified.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only changes two Dockerfile CPE labels; no Ginkgo/e2e tests were added or modified, so IPv4/disconnected-network compatibility is not applicable.
No-Weak-Crypto	✅ Passed	Only two Dockerfile cpe labels changed from el9 to el10; no weak-crypto, custom crypto, or secret comparisons were added.
Container-Privileges	✅ Passed	Diff is limited to CPE label updates in two Dockerfiles; no privileged, host*, SYS_ADMIN, root, or allowPrivilegeEscalation settings changed.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only changes Dockerfile image labels (CPE/name); no logging, secrets, or customer data exposure is introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

Hi @adchauha. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[adchauha]

/ok-to-test

[openshift-ci]

@adchauha: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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.