chore(deps): update jobset-operator-main to 30335b9

[red-hat-konflux]

Image created from 'https://github.com/openshift/jobset-operator?rev=f079bc9b7cc8d6dfd1b751e5b8e6a8616c187598'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/jobset-lws-pipeline-tenant/jobset-operator-main	digest	326658d -> 30335b9

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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
This is Konflux nudging PR, not Mintmaker.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

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: 62cffacf-0216-4e15-ad66-e6c21b3f67b5

📥 Commits

Reviewing files that changed from the base of the PR and between 0296eb9 and bec0a51.

📒 Files selected for processing (1)

• bundle.Dockerfile

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The bundle build updates the pinned OPERATOR_IMAGE digest in bundle.Dockerfile.

Changes

Operator image update

Layer / File(s)	Summary
Update pinned operator image bundle.Dockerfile	The OPERATOR_IMAGE build argument now references a different pinned image digest.

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

Merge Risk: ⚪ Minimal · up to bec0a

This dependency image update introduces no identified merge-blocking risk, so it is merge-ready after normal checks and review.

Suggested reviewers: benluddy, everettraven

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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	The diff changes only the OPERATOR_IMAGE digest in bundle.Dockerfile; it adds no Ginkgo tests or test titles, so the stability check is not applicable.
Test Structure And Quality	✅ Passed	The exact diff changes only one OPERATOR_IMAGE digest in bundle.Dockerfile; no Ginkgo test code or test behavior changed.
Microshift Test Compatibility	✅ Passed	The diff changes only the OPERATOR_IMAGE digest in bundle.Dockerfile; it adds no Ginkgo e2e tests or MicroShift-incompatible API usage.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The parent-to-HEAD diff changes only one OPERATOR_IMAGE digest in bundle.Dockerfile; it adds no Ginkgo e2e tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit changes only the OPERATOR_IMAGE digest. No deployment manifest, controller code, or topology-related scheduling constraint changed; the existing replicas: 1 is unchanged.
Ote Binary Stdout Contract	✅ Passed	The PR only changes the OPERATOR_IMAGE digest; the diff contains no OTE main or suite-setup code, so it introduces no process-level stdout violation.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes only one image digest in bundle.Dockerfile; it adds no Ginkgo tests or test networking and introduces no IPv4 or external-connectivity test condition.
No-Weak-Crypto	✅ Passed	The diff changes only the OPERATOR_IMAGE SHA-256 digest. It adds no MD5, SHA-1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparison code.
Container-Privileges	✅ Passed	The PR changes only the operator image digest. No privilege declaration changed; manifests enforce runAsNonRoot, disable privilege escalation, drop all capabilities, and Dockerfiles use USER 1001.
No-Sensitive-Data-In-Logs	✅ Passed	The exact diff changes only the OPERATOR_IMAGE digest in bundle.Dockerfile; it adds no logging or sensitive-data output.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the dependency image update and the new jobset-operator-main revision.

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ricardomaraschini 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

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