NO-JIRA: Update kueue-operand-1-3 to 7d23320

[red-hat-konflux]

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

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operand-1-3	digest	624ac18 -> 7d23320

---

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 a container image reference to a newer digest.

[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=ee2160282df7eb2500a3acf1f068c7302179ac15'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operand-1-3	digest	624ac18 -> 31c00db

---

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]

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: Enterprise

Run ID: 40791a9a-4642-41da-81c3-6014ba1bb087

📥 Commits

Reviewing files that changed from the base of the PR and between 9a1946a and fb4c4ef.

📒 Files selected for processing (1)

• related_images.json

✅ Files skipped from review due to trivial changes (1)

• related_images.json

---

Walkthrough

The related_images.json file updates the operand entry’s registry.redhat.io/kueue/kueue-rhel9 digest to a new sha256 value. No other fields changed.

Changes

Operand Image Digest Update

Layer / File(s)	Summary
Digest update related_images.json	Replaces the operand image digest for registry.redhat.io/kueue/kueue-rhel9 with a new pinned sha256 value.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/kueue-operator#2095: Updates the same operand image digest field in related_images.json to a different digest value.
• openshift/kueue-operator#2100: Also changes the operand container image digest for kueue-rhel9 in related_images.json.
• openshift/kueue-operator#2113: Modifies the operand registry.redhat.io/kueue/kueue-rhel9 digest in the same file.

Suggested labels

lgtm

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Test Structure And Quality	⚠️ Warning	The new e2e Ginkgo tests include many bare assertions (e.g. 25 in e2e_operator_test.go, 28 in e2e_visibility_on_demand_test.go) without failure context.	Add contextual failure messages to bare Expect/Should assertions and keep the existing timeout/cleanup patterns consistent across the new e2e tests.

✅ Passed checks (14 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 the kueue operand image digest to 7d23320.
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	Changed test files use only literal Ginkgo titles; no It/Describe/Context/When calls build names from dynamic values.
Microshift Test Compatibility	✅ Passed	Only related_images.json changed; no test/e2e files or Ginkgo specs were added, so MicroShift compatibility isn’t implicated.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only updates related_images.json image digest; no new Ginkgo e2e tests or SNO-sensitive code were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only related_images.json changed, updating an image digest; no manifests, controllers, replicas, affinity, selectors, or PDB logic were introduced.
Ote Binary Stdout Contract	✅ Passed	PR only updates related_images.json digest; no process-level code or stdout-writing paths were changed.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only related_images.json changed an image digest; no Ginkgo e2e test code or new connectivity/IP-family assumptions were added.
No-Weak-Crypto	✅ Passed	Only related_images.json changed, updating an OCI image digest; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons appear.
Container-Privileges	✅ Passed	Changed workload manifests keep securityContext hardened (allowPrivilegeEscalation: false, runAsNonRoot: true); no added privileged/host* settings were found.
No-Sensitive-Data-In-Logs	✅ Passed	Only related_images.json changed, updating an image digest; no logging code or sensitive data exposure is present in the diff.

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

_{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

[kannon92]

/lgtm

[openshift-ci]

@red-hat-konflux: 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.