Skip to content

WIP: Rebase release-4.22 to v1.35.6#2693

Open
JSampsonIV wants to merge 27 commits into
openshift:release-4.22from
JSampsonIV:release-4.22
Open

WIP: Rebase release-4.22 to v1.35.6#2693
JSampsonIV wants to merge 27 commits into
openshift:release-4.22from
JSampsonIV:release-4.22

Conversation

@JSampsonIV

Copy link
Copy Markdown

Rebase completed by redhat-chai-bot using script created by JSampsonIV

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


k8s-release-robot and others added 26 commits May 12, 2026 10:02
When collecting all matching devices for AllocationModeAll, the allocator did not record the source pool on the candidate device. Devices with consumed counters use that pool when checking shared counter availability, which caused kube-scheduler to panic.

Set the pool on all-devices candidates in the stable, incubating, and experimental allocators, and add a shared regression test for AllocationModeAll with consumed counters.
When calling ControllerSELinuxTranslator.Conflicts(), the SELinux label
is repeatedly split into []string to detect conflicts. This causes a huge
number of allocations when there are many comparisons.

This is now made more efficient by pre-parsing the SELinux label and
storing it in podInfo as [4]string for fast comparison when needed.
Added podToVolumes reverse index to optimize DeletePod.
Currently we simply iterate through all the volumes and remove the pod
being deleted from there. This is inefficient and takes longer the
longer the volume list becomes.

Keeping a map pod -> volumes makes removing a pod fast. We can just jump
to the relevant volumes directly and remove the pod from there.
Also prevent duplicate metric emissions
Thread the reconciler's existing isRemount signal into MounterArgs so
volume plugins can distinguish an initial publish from a republish
(e.g. CSIDriver.spec.requiresRepublish=true). No behavior change.
On a remount (e.g. CSIDriver.spec.requiresRepublish=true), the volume is
already published and the pod is observing the existing bind mount.
Removing the mount dir on a NodePublish error left the pod with stale
contents that subsequent successful republishes could not repair.
Accessing svc.Spec.IPFamilies[0] without a bounds check panics when a
service reaches the controller with an empty IPFamilies field. This can
happen via watch events: the apiserver's defaultOnRead decorator populates
IPFamilies on GET/LIST but not on watch (cachingObject wrapping bypasses
the type assertion).

Restore the inference logic removed in kubernetes#130101: fall back to ClusterIP
for headful services and pod IP for headless services.

Signed-off-by: Rahul <rahulbabu95@gmail.com>
Signed-off-by: bo.jiang <bo.jiang@daocloud.io>
[1.35] Restore ability to plumb binary data through envvar values
…selinux-metrics-perf

Manual cherry pick selinux metrics perf
…y-pick-of-#138736-upstream-release-1.35

Automated cherry pick of kubernetes#138736: fix: avoid panic on services with empty IPFamilies
…ck-of-#139017-upstream-release-1.35

Automated cherry pick of kubernetes#139017: Fix dra scoring bug with mixed allocated and unallocated claims
…-of-#138885-origin-release-1.35

Automated cherry pick of kubernetes#138885: DRA: fix AllocationModeAll with consumed counters
…ck-of-#139045-upstream-release-1.35

Automated cherry pick of kubernetes#139045: fix(csi): preserve mount dir when NodePublish fails on a remount
…pick-of-#139480-origin-release-1.35

Automated cherry pick of kubernetes#139480: Fix wrong marking of errors
…-pick-of-#139339-upstream-release-1.35

Automated cherry pick of kubernetes#139339: kubeadm: fix dry-run CA copy paths in init certs
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
…l135

[release-1.35] [go]Bump images and versions to go 1.25.11 and distroless iptables
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jun 15, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 15, 2026
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 72d77c15-8e42-4253-ad7c-ef38356df09b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci-robot

Copy link
Copy Markdown

@JSampsonIV: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci Bot requested review from deads2k and rphillips June 15, 2026 13:58
@openshift-ci openshift-ci Bot added the vendor-update Touching vendor dir or related files label Jun 15, 2026
@openshift-ci

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Copy link
Copy Markdown

@JSampsonIV: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@JSampsonIV

Copy link
Copy Markdown
Author

/retest

1 similar comment
@JSampsonIV

Copy link
Copy Markdown
Author

/retest

@jubittajohn

Copy link
Copy Markdown

/test images

@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown

@JSampsonIV: 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/e2e-metal-ipi-ovn-ipv6 6228532 link true /test e2e-metal-ipi-ovn-ipv6

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.

@jubittajohn

Copy link
Copy Markdown

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.