NO-JIRA: Update registry.redhat.io/ubi9/ubi-minimal Docker digest to 83006d5

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.redhat.io/ubi9/ubi-minimal	final	digest	161a4e2 -> 83006d5

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign brandisher 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-robot]

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

Details

In response to this:

This PR contains the following updates:

Package	Type	Update	Change
registry.redhat.io/ubi9/ubi-minimal	final	digest	161a4e2 -> c7d4414

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: d758021d-a12f-4774-8f0b-73715d896c2c

📥 Commits

Reviewing files that changed from the base of the PR and between 3151ff4 and fe6c72c.

📒 Files selected for processing (1)

• release/operator/konflux.Dockerfile

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

• release/operator/konflux.Dockerfile

---

Walkthrough

The Dockerfile's final-stage base image digest for registry.redhat.io/ubi9/ubi-minimal was updated to a new SHA256 value; no other Dockerfile instructions were changed.

Changes

Cohort / File(s)	Summary
Base image digest update release/operator/konflux.Dockerfile	Updated base image digest from sha256:161a4e29… to sha256:83006d53….

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately describes the main change: updating a Docker image digest in the Dockerfile.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	PR modifies only Dockerfile, not test files. Ginkgo test naming check does not apply.
Test Structure And Quality	✅ Passed	PR modifies only konflux.Dockerfile with no Ginkgo test code changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/main/registry.redhat.io-ubi9-ubi-minimal

📝 Coding Plan

• Generate coding plan for human review comments

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@release/operator/konflux.Dockerfile`:
- Line 23: The FROM instruction in konflux.Dockerfile references a non-existent
digest causing CI failures; verify the sha256 value used in the FROM line (the
registry.redhat.io/ubi9/ubi-minimal@sha256:69f5c9886ecb19b23e88275a5cd904c47dd982dfa370fbbd0c356d7b1047ef68
entry) against the Red Hat registry and update it to the correct digest or
replace it with a known-good tag (e.g., a stable ubi9/ubi-minimal tag) so the
image can be pulled, then re-run the verification script to confirm the digest
exists before merging.

---

ℹ️ Review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro

Run ID: 4aa4eabe-ab87-47e6-8053-3b21ecce5cf5

📥 Commits

Reviewing files that changed from the base of the PR and between b5e0e11 and db9d139.

📒 Files selected for processing (1)

• release/operator/konflux.Dockerfile

[openshift-ci]

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/precommit-check	fe6c72c	link	true	/test precommit-check

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.