Skip to content

NO-JIRA: Update kueue-operator-main to 262a979#2075

Merged
openshift-merge-bot[bot] merged 1 commit into
mainfrom
konflux/component-updates/component-update-kueue-operator-main
Jun 26, 2026
Merged

NO-JIRA: Update kueue-operator-main to 262a979#2075
openshift-merge-bot[bot] merged 1 commit into
mainfrom
konflux/component-updates/component-update-kueue-operator-main

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

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

This PR contains the following updates:

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

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 image reference to a new container digest in the release metadata.
    • No user-facing behavior, settings, or other references were changed.

@red-hat-konflux red-hat-konflux Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. konflux-nudge lgtm Indicates that a PR is ready to be merged. labels Jun 23, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@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=1b9c906998e7e16fe165d3c3dab85b022c1230a0'

This PR contains the following updates:

Package Update Change
quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main digest 24721e0 -> 8a71752

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 23, 2026
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

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: 6a5596ef-05a0-4b45-a5c2-a7bde42c9668

📥 Commits

Reviewing files that changed from the base of the PR and between ab4602b and ca19666.

📒 Files selected for processing (2)
  • related_images.developer.json
  • related_images.json
✅ Files skipped from review due to trivial changes (1)
  • related_images.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • related_images.developer.json

Walkthrough

The operator image SHA256 digest is updated in both related_images.developer.json and related_images.json. Only the digest value changes; the registry path, repository, tag, and all other image entries remain unchanged.

Changes

Operator Image Digest Bump

Layer / File(s) Summary
Operator image digest update
related_images.developer.json, related_images.json
The operator image entry is updated to a new SHA256 digest in both manifest files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • openshift/kueue-operator#2041: Updates the same operator image reference in related_images.developer.json and related_images.json by changing only the kueue-operator-main SHA256 digest.
  • openshift/kueue-operator#2049: Updates the operator image digest in the same two image reference files with the same digest-only change pattern.
  • openshift/kueue-operator#2053: Also changes the operator SHA256 digest in related_images.developer.json and related_images.json.

Suggested labels

lgtm

🚥 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 describes the main change: updating kueue-operator-main to the new digest 262a979.
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 related_images*.json changed; no test files or Ginkgo titles were modified, so there are no unstable test names to flag.
Test Structure And Quality ✅ Passed Only related_images.json and related_images.developer.json changed; no Ginkgo test code was touched, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only related_images JSON digests changed; no Ginkgo tests or MicroShift-unsupported APIs were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only updates image digests in related_images*.json; no Ginkgo e2e tests or node-topology assumptions were added.
Topology-Aware Scheduling Compatibility ✅ Passed Only image digests in related_images*.json changed; no deployment, operator, or scheduling manifests/code were modified.
Ote Binary Stdout Contract ✅ Passed Only related_images JSON digest files changed; no process-level Go code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only related_images.json and related_images.developer.json changed; no Ginkgo e2e tests or network-using test code were added.
No-Weak-Crypto ✅ Passed Only image digest JSONs changed; both files contain no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or secret-comparison code.
Container-Privileges ✅ Passed Only related_images*.json changed; no container/K8s manifests or privilege settings were introduced.
No-Sensitive-Data-In-Logs ✅ Passed The only changed files are related_images*.json, and they contain image references/digests only; no passwords, tokens, PII, or log content was present.
✨ 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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: Remove the trailing space from the image property value in the
related_images.developer.json file. The image digest currently has a space after
the SHA256 hash and before the closing quote, which will cause the image
reference to be malformed when extracted by jq in bundle.developer.Dockerfile.
Delete this trailing whitespace to ensure the image reference is properly
formed.
🪄 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: 8e8e8104-5a12-4b94-9cbf-01c7984975bb

📥 Commits

Reviewing files that changed from the base of the PR and between 1b9c906 and 297e5ee.

📒 Files selected for processing (2)
  • related_images.developer.json
  • related_images.json

Comment thread related_images.developer.json Outdated
{
"name": "operator",
"image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:24721e03eb71e62ed7a8e36d7600ffe5246d33535b57f6a08d934d2cf268c8d4 "
"image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:8a71752eddcf856321e98f67dfa6701d6681574458c9a40af6317d120e2a6678 "

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🔴 Critical | ⚡ Quick win

Remove trailing space from the image digest.

The image value contains a trailing space after the SHA256 digest (before the closing quote). This will cause the image reference to be malformed when extracted by jq in bundle.developer.Dockerfile, likely resulting in image pull failures during deployment.

🐛 Proposed fix to remove trailing space
-    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:8a71752eddcf856321e98f67dfa6701d6681574458c9a40af6317d120e2a6678 "
+    "image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:8a71752eddcf856321e98f67dfa6701d6681574458c9a40af6317d120e2a6678"
📝 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:8a71752eddcf856321e98f67dfa6701d6681574458c9a40af6317d120e2a6678 "
"image": "quay.io/redhat-user-workloads/kueue-operator-tenant/kueue-operator-main@sha256:8a71752eddcf856321e98f67dfa6701d6681574458c9a40af6317d120e2a6678"
🤖 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, Remove the trailing space from the
image property value in the related_images.developer.json file. The image digest
currently has a space after the SHA256 hash and before the closing quote, which
will cause the image reference to be malformed when extracted by jq in
bundle.developer.Dockerfile. Delete this trailing whitespace to ensure the image
reference is properly formed.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1b9c906 and 2 for PR HEAD 297e5ee in total

@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update kueue-operator-main to 8a71752 NO-JIRA: Update kueue-operator-main to be41486 Jun 24, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/component-updates/component-update-kueue-operator-main branch from 297e5ee to ab4602b Compare June 24, 2026 03:28
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 24, 2026
@kannon92

Copy link
Copy Markdown
Contributor

/retest

@kannon92

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2026
Image created from 'https://github.com/openshift/kueue-operator?rev=6f780c8860f1202d341f64820e93689c56a0e305'

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot changed the title NO-JIRA: Update kueue-operator-main to be41486 NO-JIRA: Update kueue-operator-main to 262a979 Jun 26, 2026
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/component-updates/component-update-kueue-operator-main branch from ab4602b to ca19666 Compare June 26, 2026 03:53
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2026
@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

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

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

@kannon92

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD ab82cd6 and 2 for PR HEAD ca19666 in total

@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

@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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 8ecfd2a into main Jun 26, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. konflux-nudge lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants