chore(deps): update osc-storage-helper to 6cecb78

[red-hat-konflux]

Image created from 'https://github.com/openshift/confidential-compute-artifacts?rev=b54c8e3b1d8f571fa6d7388fae31289614b1dba8'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/ose-osc-tenant/osc-storage-helper	digest	140a80f -> 6cecb78

---

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

[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: 20caa077-e81c-4103-b572-a389285f23d2

📥 Commits

Reviewing files that changed from the base of the PR and between ec06edf and 07a2ab0.

📒 Files selected for processing (2)

• bundle/manifests/sandboxed-containers-operator.clusterserviceversion.yaml
• config/manager/manager.yaml

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

• config/manager/manager.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• bundle/manifests/sandboxed-containers-operator.clusterserviceversion.yaml

---

📝 Walkthrough

Walkthrough

The osc-storage-helper container image digest is updated in two manifest files. In config/manager/manager.yaml, the RELATED_IMAGE_STORAGE_HELPER environment variable is updated with a new SHA256 digest. In bundle/manifests/sandboxed-containers-operator.clusterserviceversion.yaml, the same environment variable in the controller-manager container spec and the storage-helper entry under spec.relatedImages are both updated to the new digest.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/sandboxed-containers-operator#2331: Updates container image digests in operator-related manifests as part of the same dependency update cycle.

Suggested reviewers

• pmores
• tbuskey

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the osc-storage-helper image to a specific digest (6cecb78).
Description check	✅ Passed	The description is related to the changeset, providing details about the image digest update and referencing the source commit.
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	This PR only modifies YAML configuration files (bundle manifests and Kubernetes deployment configs) to update container image digests. No test files are modified, making the Ginkgo test name stabil...
Test Structure And Quality	✅ Passed	PR contains only configuration/manifest updates (image digest changes), no Ginkgo test code modifications. The check is not applicable as it requires reviewing test code.
Microshift Test Compatibility	✅ Passed	No Ginkgo e2e tests were added in this PR. New tests are standard Go unit tests and Python unit tests, which fall outside the scope of this MicroShift compatibility check.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR contains no new Ginkgo e2e tests; changes are limited to image digest updates in YAML configuration files (manager.yaml and clusterserviceversion.yaml). Check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR only updates container image digests for osc-storage-helper; no scheduling constraints, deployment configs, replica counts, or topology-related settings were modified or introduced.
Ote Binary Stdout Contract	✅ Passed	PR only modifies YAML configuration files to update container image digests; contains no Go code changes that could violate OTE stdout contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo e2e tests (It/Describe/Context/When blocks) were added in this PR. Changes are image digest updates in config files and standard Go unit tests.
No-Weak-Crypto	✅ Passed	PR updates only container image digests in YAML manifests with no weak cryptographic algorithms, custom crypto implementations, or unsafe patterns detected.
Container-Privileges	✅ Passed	No container privilege escalation concerns detected. Manifests have allowPrivilegeEscalation=false, runAsNonRoot=true, no hostPID/hostNetwork/hostIPC, no SYS_ADMIN capabilities, and caps dropped. C...
No-Sensitive-Data-In-Logs	✅ Passed	PR modifies only image digest references in deployment configuration files; no logging statements are added or modified that could expose sensitive data.

_{✏️ 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/component-updates/osc-operator-bundle-component-update-osc-storage-helper

---

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

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.