NO-ISSUE: Synchronize From Upstream Repositories

[openshift-bot]

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-04-27 15:00:54	operator-framework/operator-lifecycle-manager@adc7ebf	dependabot[bot]	🌱 Bump the k8s-dependencies group with 8 updates (#3816)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/assign @openshift/openshift-team-operator-runtime

[openshift-ci-robot]

@openshift-bot: This pull request explicitly references no jira issue.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-04-27 15:00:54	operator-framework/operator-lifecycle-manager@adc7ebf	dependabot[bot]	🌱 Bump the k8s-dependencies group with 8 updates (#3816)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/assign @openshift/openshift-team-operator-runtime

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 87aeeaef-1164-47ed-9338-6a25e98e04ed

📥 Commits

Reviewing files that changed from the base of the PR and between 122728c and 4e8ff81.

⛔ Files ignored due to path filters (5)

• go.sum is excluded by !**/*.sum
• staging/operator-lifecycle-manager/go.sum is excluded by !**/*.sum
• vendor/k8s.io/apimachinery/pkg/api/validate/union.go is excluded by !**/vendor/**, !vendor/**
• vendor/k8s.io/apiserver/pkg/endpoints/filters/audit.go is excluded by !**/vendor/**, !vendor/**
• vendor/modules.txt is excluded by !**/vendor/**, !vendor/**

📒 Files selected for processing (2)

• go.mod
• staging/operator-lifecycle-manager/go.mod

---

Walkthrough

Updates Kubernetes Go module dependencies from v0.35.3 to v0.35.4 across two go.mod files. Core packages like k8s.io/api, k8s.io/client-go, and related modules are bumped uniformly, with no changes to public APIs.

Changes

Cohort / File(s)	Summary
Kubernetes dependency version bump go.mod, staging/operator-lifecycle-manager/go.mod	Kubernetes Go modules updated from v0.35.3 to v0.35.4, including k8s.io/api, k8s.io/apimachinery, k8s.io/client-go, k8s.io/code-generator, k8s.io/apiserver, k8s.io/component-base, k8s.io/apiextensions-apiserver, k8s.io/kms, and k8s.io/kube-aggregator.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'NO-ISSUE: Synchronize From Upstream Repositories' accurately describes the main change—pulling in Kubernetes dependency updates from upstream repositories.
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	PR contains only dependency version updates in go.mod files with no modifications to Ginkgo test files, making this check not applicable.
Test Structure And Quality	✅ Passed	PR contains only dependency version updates with no Ginkgo test files modified.
Microshift Test Compatibility	✅ Passed	PR contains only dependency version updates with no new Ginkgo e2e tests added, making the MicroShift test compatibility check not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only contains Kubernetes dependency version updates in go.mod files with no new Ginkgo e2e tests being added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR contains only Kubernetes Go module dependency version updates with no modifications to deployment manifests, operator code, controllers, or scheduling configuration.
Ote Binary Stdout Contract	✅ Passed	PR is a dependency version bump updating Kubernetes packages from v0.35.3 to v0.35.4 with no executable code changes to the OTE binary, which uses only framework-managed output.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR only updates Kubernetes dependency versions in go.mod files with no new Ginkgo e2e tests added.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-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:

• DOWNSTREAM_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: openshift-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:

• DOWNSTREAM_OWNERS

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

[perdasilva]

/retest

[perdasilva]

/verified bypass

this is just a dependency update - as long as CI is green this should be ok

[openshift-ci-robot]

@perdasilva: The verified label has been added.

Details

In response to this:

/verified bypass

this is just a dependency update - as long as CI is green this should be ok

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.

[perdasilva]

/retest

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 122728c and 2 for PR HEAD 4e8ff81 in total

[perdasilva]

/retest