Skip to content

WIP: OCPBUGS-76516: Bump v1.34.4#2590

Open
jubittajohn wants to merge 84 commits intoopenshift:release-4.21from
jubittajohn:rebase-v1.34.4
Open

WIP: OCPBUGS-76516: Bump v1.34.4#2590
jubittajohn wants to merge 84 commits intoopenshift:release-4.21from
jubittajohn:rebase-v1.34.4

Conversation

@jubittajohn
Copy link

Bump release-4.21 to v1.34.4 from v1.34.2

eltrufas and others added 30 commits November 3, 2025 15:47
Certain failures during SetupDevice and MapPodDevice are not treated as
transient in the csi raw block plugin implementation, while they are in
the file mode plugin. This can lead to certain failures causing volumes
to be marked as unmounted incorrectly.

This patch brings the block plugin up to parity with the fs one by
marking the equivalent calls as transient. This mostly covers API server
and some csi driver calls.
Fixes issue kubernetes#134023 where alpha API warnings were being logged
when binary version (1.34.1) and emulation version (1.34) differed
only in patch version.

The issue was in api_enablement.go where the version comparison
was using EqualTo() which compares all version components including
patch versions. The fix changes the comparison to only check
major.minor versions using version.MajorMinor().

Changes:
- Modified version comparison logic in ApplyTo() method to only
  compare major.minor versions, not patch versions
- Added comprehensive test cases to verify the fix works correctly
- Tests confirm that warnings are still logged for different
  major/minor versions but not for different patch versions

This prevents spurious warnings when emulation version is set to
major.minor (e.g., 1.34) and binary version includes patch (e.g., 1.34.1).
Signed-off-by: Andrey Borovets <andrey.borovets@flant.com>

add import

Signed-off-by: Andrey Borovets <andrey.borovets@flant.com>

delete import
…ess iptables

Signed-off-by: Carlos Panato <ctadeu@gmail.com>
[release-1.34][go] Bump dependencies, images and versions used to Go 1.24.10 and distroless iptables
…pick-of-#135359-origin-release-1.34

Automated cherry pick of kubernetes#135359: Fallback to live ns lookup on admission if lister cannot find namespace
…-pick-of-#135327-upstream-release-1.34

Automated cherry pick of kubernetes#135327: Fix alpha API warnings for patch version differences
…ealFIFO are implementing it

Signed-off-by: Valerian Roche <valerian.roche@datadoghq.com>
…herry-pick-of-#135153-upstream-release-1.34

Automated cherry pick of kubernetes#135153: mark device manager as haelthy before it started for the first time
…pick-of-#135580-upstream-release-1.34

Automated cherry pick of kubernetes#135580 - Embed proper interface in TransformingStore
…ess iptables

Signed-off-by: Carlos Panato <ctadeu@gmail.com>
[release-1.34][go] Bump dependencies, images and versions used to Go 1.24.11 and distroless iptables
…rol-plane-join-1-34

[Manual bugfix]: unhide the etcd-join phase for v1.34
…ick-of-#133599-upstream-release-1.34

Automated cherry pick of kubernetes#133599: Mark API server errors as transient in csi raw block driver
The kubekins image got updated from containerd 1.7 to 2.2, which broke
local-up-cluster.sh in the CI because more recent containerd uses single
quotation marks around strings instead of double quotation marks as before. The
search/replaced with sed no longer matched, causing containerd to fail mounting
overlayfs on the default /var/lib/containerd. We have to use the emptyDir host
mount under /docker-graph.

The fix is to relax the search term slightly so that it accepts both kinds of
quotation marks.
`make` was printing the following warning on Ubuntu 25.10,
which switched away from GNU coreutils to uutils:

```
!!! [1107 12:46:24] Failed to find GNU date as date or gdate. If you are on Mac: brew install coreutils.
<GOPATH>/src/k8s.io/kubernetes/hack/lib/version.sh: line 166: DATE: unbound variable
```

Fix issue 135210

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
(cherry picked from commit 0c0bc0d)
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
This metric got broken by caching efforts -- the value is counted only once.
If the user has provided extraArgs with an order that has
significance (e.g. --service-account-issuer for kube-apiserver),
kubeadm will correctly override any base args, but will end up
sorting the entire resulting list, which is not desired.

Instead, only sort the base arguments and preserve the order
of overrides provided by the user.
…-of-#135692-origin-release-1.34

Automated cherry pick of kubernetes#135692: local-up-cluster.sh: support more recent containerd like 2.2
dims and others added 16 commits January 29, 2026 15:02
- Use netutils.IsIPv6(ip) instead of manual nil/To4 check
- Remove unnecessary ip.To16() call since IPv6 is already 16 bytes
- Remove ipFamily from grep pattern since IP format ensures correctness

Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
…of-#136529-kubernetes#136554-upstream-release-1.34

Automated cherry pick of kubernetes#136529: test: Read /proc/net/nf_conntrack instead of using conntrack binary
kubernetes#136554: test: Fix KubeProxy CLOSE_WAIT test for IPv6 environments (and where /proc/net/nf_conntrack may be missing)
…ess iptables

Signed-off-by: Carlos Panato <ctadeu@gmail.com>
[release-1.34] [go] Bump dependencies, images and versions used to Go 1.24.12 and distroless iptables
…rry-pick-of-#136241-upstream-release-1.34

Automated cherry pick of kubernetes#136241: Fix for preferred dualstack and required dualstack in winkernel proxier.
…release-1.34

[release-1.34] fix(kubelet): convert V().Error() to V().Info() for verbosity-aware logging
…-of-#136269-origin-release-1.34

Automated cherry pick of kubernetes#136269: DRA scheduler: double allocation fixes
…-cherry-pick-of-#135666-upstream-release-1.34

Automated cherry pick of kubernetes#135666: Fixes the flaky `TestWebhookConverterWithWatchCache` test
…y-pick-of-#136202-upstream-release-1.34

Automated cherry pick of kubernetes#136202: csi: raise kubelet CSI init backoff to cover ~140s DNS delays
…y-pick-of-#136014-upstream-release-1.34

Automated cherry pick of kubernetes#136014: kubeadm: waiting for etcd learner member to be started before promoting during 'kubeadm join'
…erry-pick-of-#135919-upstream-release-1.34

Automated cherry pick of kubernetes#135919: kubelet(dra): fix handling of multiple ResourceClaims when one is already prepared
…ick-of-#136325-upstream-release-1.34

Automated cherry pick of kubernetes#136325: fix(expansion):Resolve the issue of UTF-8 characters being truncated
Kubernetes official release v1.34.4
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 11, 2026
@openshift-ci-robot
Copy link

@jubittajohn: This pull request references Jira Issue OCPBUGS-76516, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-76516 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bump release-4.21 to v1.34.4 from v1.34.2

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.

@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 Feb 11, 2026
@openshift-ci-robot
Copy link

@jubittajohn: 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 benluddy and sjenning February 11, 2026 17:39
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Feb 11, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@jubittajohn
Copy link
Author

/test e2e-azure-ovn-upgrade

@bertinatto
Copy link
Member

/test images

@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@openshift-ci
Copy link

openshift-ci bot commented Feb 12, 2026

@jubittajohn: 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.

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.