Skip to content

OCPBUGS-93896: Rebase v1.33.13 in release-4.20#7

Open
JSampsonIV wants to merge 46 commits into
release-4.20from
rebase-v1.33.13
Open

OCPBUGS-93896: Rebase v1.33.13 in release-4.20#7
JSampsonIV wants to merge 46 commits into
release-4.20from
rebase-v1.33.13

Conversation

@JSampsonIV

Copy link
Copy Markdown
Owner

haojiwu and others added 30 commits March 12, 2026 13:10
Fixes kube-proxy's nftables mode to work on systems with nft 1.1.3.
…-pick-of-#137501-origin-release-1.33

Automated cherry pick of kubernetes#137501: Fix kube-proxy on systems with nft 1.1.3 (take 2)
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
…cherry-pick-of-#133624-upstream-release-1.33

Automated cherry pick of kubernetes#133624: Fix flaking RunTestDelayedWatchDelivery
…release-1.33

[release-1.33] Fix RepairIPAddress controller startup failure when namespace informer is not yet synced
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
[release-1.33] Bump images and versions to go 1.25.9 and distroless iptables
Kubernetes-commit: 7e9c2c8eef26f99aa2f94d8e09d6d32de86c7769
[release-1.33] Update go.opentelemetry.io/otel to v1.41.0
…-v0.5.1-1.33

[1.33] Update github.com/moby/spdystream from v0.5.0 to v0.5.1
Kubernetes official release v1.33.11
Signed-off-by: Benjamin Wang <benjamin.ahrtr@gmail.com>
Signed-off-by: Benjamin Wang <benjamin.ahrtr@gmail.com>
…-of-#138403-upstream-release-1.33

Automated cherry pick of kubernetes#138403: kubeadm: Evaluate etcd cluster health using quorum
Historicaly the kubeadm clients have used the 'admin.conf'
and 'super-admin.conf' directly, which makes all API calls
go trough the CPE (control plane endpoint). This can create
problems for scenarios when the LB is provisioned only after
'init' starts the kube-apiserver.

Instead of using the '.conf' as they are, modify them
in memory to point to the LAE (localAPIEndpoint).
This was already done by the WaitControlPlaneClient for
the WaitControlPlane phase, which required it. This separate
client is no longer needed.

However, do use a unmodified kubeconfig to the init phase
bootstrap-token since this is the phase that creates
the cluster-info CM and for that we need the original CPE
server address.
"OCPBUGS-83609: Bump to k8s v1.33.11"
FetchInitConfigurationFromCluster always called SetAPIEndpointDynamicDefaults,
which invokes ChooseAPIServerBindAddress and requires a default route on the
host. Worker nodes joining the cluster don't need a LocalAPIEndpoint and may
legitimately have no default route, causing kubeadm join to fail with:

```
unable to fetch the kubeadm-config ConfigMap: unable to select an IP from
default routes.
```

Add a skipAPIEndpoint parameter to SetInitDynamicDefaults and pass
`!getAPIEndpoint` from FetchInitConfigurationFromCluster, so the endpoint
defaulter is bypassed when the caller did not request the endpoint (worker
join, non-control-plane reset/certs/upgrade paths).

Signed-off-by: Seena Fallah <seenafallah@gmail.com>
Signed-off-by: Micah Hausler <mhausler@amazon.com>
…pick-of-#138957-origin-release-1.33

Automated cherry pick of kubernetes#138957: kubeadm: use dedicated ClusterRole for apiserver kubelet client
k8s-ci-robot and others added 16 commits May 11, 2026 21:51
…pick-of-#138449-origin-release-1.33

Automated cherry pick of kubernetes#138449: kubeadm: use the localAPIEndpoint for all API calls in 'init'
…pick-of-#138692-origin-release-1.33

Automated cherry pick of kubernetes#138692: kubeadm: skip LocalAPIEndpoint defaulting on worker join
Kubernetes official release v1.33.12
Signed-off-by: jubittajohn <jujohn@redhat.com>
OCPBUGS-85501: Bump Kubernetes v1.33.12 to release-4.20
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>
Using a CRD group of "stable.<unique-name>" causes the conformance test
"Discovery should validate PreferredVersion for each APIGroup" to see the
group in discovery before its preferred version is populated, resulting in
intermittent failures (~4-5%). Adding ".example.com" suffix uses a known
example domain that avoids triggering the race.

Upstream: kubernetes#133509
…y-pick-of-#138736-upstream-release-1.33

Automated cherry pick of kubernetes#138736: fix: avoid panic on services with empty IPFamilies
…rry-pick-2677-to-release-4.20

[release-4.20] OCPBUGS-87173: fix flake race in VAP e2e case
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
…l133

[release-1.33] [go] Bump images and versions to go 1.25.11 and distroless iptables
Kubernetes official release v1.33.13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.