NO-JIRA: Update kueue-operator-main to 3b03501

[red-hat-konflux]

Image created from 'https://github.com/openshift/kueue-operator?rev=10bd238e5cbfec090ffd55f2582a6ab26b64cd3c'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main	digest	262a979 -> 3b03501

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test

Summary by CodeRabbit

• Chores
  • Updated the operator container image reference to a newer digest.
  • Kept all other image entries unchanged.

[openshift-ci-robot]

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Image created from 'https://github.com/openshift/kueue-operator?rev=10bd238e5cbfec090ffd55f2582a6ab26b64cd3c'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main	digest	262a979 -> 3b03501

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Walkthrough

The operator container image digest is updated in both related_images.developer.json and related_images.json, replacing the previous sha256 digest with a new one. No other entries are modified.

Changes

Operator Image Digest Bump

Layer / File(s)	Summary
Operator image digest update related_images.developer.json, related_images.json	The operator entry's image digest is replaced with a new sha256 value in both related images JSON files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/kueue-operator#2075: Same type of operator image digest update in both related_images.developer.json and related_images.json.
• openshift/kueue-operator#2094: Updates the operator container image digest in related_images.json to a new sha256 value.
• openshift/kueue-operator#2099: Updates the operator image digest in related_images.json to a new quay sha256 value.

🚥 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 accurately and concisely describes the main change: updating kueue-operator-main to the new digest.
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	PASS: The PR only updates related_images JSON manifests; no Ginkgo test definitions or title strings were added or modified.
Test Structure And Quality	✅ Passed	The PR only updates related_images JSON digests; no Ginkgo test files or test logic are touched, so this check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only updates two related_images JSON digests; no new or modified Ginkgo tests or MicroShift-sensitive APIs were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only updates related_images JSON digests; no Go/Ginkgo/e2e tests were added or modified, so no SNO-specific assumptions are introduced.
Topology-Aware Scheduling Compatibility	✅ Passed	Only image digest entries in related_images*.json were updated; no deployment manifests, operator code, or controllers changed, so no topology-aware scheduling impact.
Ote Binary Stdout Contract	✅ Passed	PR only changes related_images JSON image digests; no process-level code or stdout/logging paths are modified.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only updates related_images JSON digests; no new Ginkgo e2e tests or networking code were added, so this check is not applicable.
No-Weak-Crypto	✅ Passed	PR only updates container image digests in JSON; no weak ciphers, custom crypto, or secret comparisons are introduced.
Container-Privileges	✅ Passed	PR only updates image digests; the deployment and CSV already set runAsNonRoot:true, allowPrivilegeEscalation:false, and drop ALL.
No-Sensitive-Data-In-Logs	✅ Passed	Only image digests were updated in two JSON manifests; no logs, secrets, PII, or other sensitive data were added.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/component-updates/component-update-kueue-operator-main

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

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:

• OWNERS

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

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:

• OWNERS

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

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:

• OWNERS

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@related_images.developer.json`:
- Line 4: The image pull spec in related_images.developer.json contains a
trailing space, which will be copied verbatim into the generated CSV by
bundle.developer.Dockerfile. Remove the extra whitespace from the image value so
the related image reference is valid and consistently used in the bundle output.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 90698940-1b48-4687-8158-565865e01700

📥 Commits

Reviewing files that changed from the base of the PR and between 10bd238 and 0a68f6d.

📒 Files selected for processing (2)

• related_images.developer.json
• related_images.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Remove the trailing space from the image reference.

That space becomes part of the pull spec, and bundle.developer.Dockerfile copies this value verbatim into the CSV, so the generated manifest can end up with an invalid operator image.

Proposed fix

-    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:3b035012a3318d168b07d8f1e3e4768be76bc70acc59ce0d44f554d3800fade0 "
+    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:3b035012a3318d168b07d8f1e3e4768be76bc70acc59ce0d44f554d3800fade0"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:3b035012a3318d168b07d8f1e3e4768be76bc70acc59ce0d44f554d3800fade0 "
	"image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:3b035012a3318d168b07d8f1e3e4768be76bc70acc59ce0d44f554d3800fade0"

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@related_images.developer.json` at line 4, The image pull spec in
related_images.developer.json contains a trailing space, which will be copied
verbatim into the generated CSV by bundle.developer.Dockerfile. Remove the extra
whitespace from the image value so the related image reference is valid and
consistently used in the bundle output.

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 10bd238 and 2 for PR HEAD 0a68f6d in total

[openshift-ci]

@red-hat-konflux[bot]: all tests passed!

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.