Week Ending August 02, 2026

Developer News

• The Kubernetes Steering Committee held a Q&A session for election candidates at the public Steering meeting on Wednesday, August 5.

• SIG ContribEx has merged documentation for the Kubernetes social media automation process, formalizing how community posts across project accounts are triaged, drafted, and published.

Election Updates

• Voting for the 2026 Kubernetes Steering Committee election will begin on August 14.
• Kaslin Fields, Priyanka Saggu and Jack Francis joined the candidate list this week.
• Candidates are reminded of Kubernetes' existing campaigning guidelines, including its policy against excessive campaigning.

Contributor Blog

KCD Around the World is a new series exploring Kubernetes Community Days through the volunteers, contributors, organizers, and attendees who make them happen. In the first edition, Kashish Verma interviews KCD New York 2026 organizer Christopher Tineo about what makes the New York community unique and the moments, conversations, and people that made this year's event special.

Release Schedule

Next Deadline: Docs Freeze, August 5; Release blog ready to review, August 13

We are in Docs Freeze. The Kubernetes v1.37 release blog will reach the "Ready for Review" milestone on August 13 as the release team continues preparing for the v1.37 release.

The target date for this month's patch releases is next week, August 11.

Featured PRs

141041: Fix CPU Manager re-allocations for pods using pod-level resources after kubelet restarts

lukaszwojciechowski fixed a kubelet CPU Manager bug that could re-allocate CPUs incorrectly for pods using pod-level resources after a kubelet restart. The bug affected pods with pod-level exclusive CPU assignments under the static CPU Manager policy. Before this fix, kubelet could either reject a restored pod with "not enough cpus available" or move it to different CPUs, leaking the original exclusive CPUs. The PR adds a restore path that reuses the checkpointed pod-level CPU set and container assignments instead of blindly allocating again.

141057: Fix StatefulSet parallel scale down after failed scale up

suii2210 fixed a StatefulSet reconciliation deadlock that could leave podManagementPolicy: Parallel workloads stuck after a failed scale-up. A partially successful rollout could leave a missing desired Pod and an out-of-range condemned Pod at the same time. If creation of the missing Pod failed because of ResourceQuota, the controller previously returned before deleting the condemned Pod, so the quota was never released and reconciliation could not make progress. This PR changes the ordering for Parallel StatefulSets so condemned Pods are processed before missing desired replicas. The existing OrderedReady behavior is unchanged.

KEP of the Week

KEP-5278: Nominated node name for an expected pod placement

This proposal extends the use of Kubernetes NominatedNodeName so the scheduler can record a pod's expected node placement at the beginning of the binding cycle, rather than using it only for preemption. The goal is to make the scheduler's internal node reservation visible to other components, such as the Cluster Autoscaler, which may otherwise incorrectly treat the node as underutilized and delete it while the pod is still in the binding phase (for example, during PreBind volume or device allocation). By exposing the expected placement through NominatedNodeName, external components can make better decisions, and the scheduler can also retain scheduling decisions across restarts, allowing PreBind operations to resume on the same node. This improves coordination between the scheduler, autoscaling, and resource allocation mechanisms such as DRA ResourceClaims. NominatedNodeName is in Beta since v1.35.

Subprojects and Dependency Updates

• cluster-api v1.14.0-beta.1: allow ClusterClass metadata patches, add cluster-api-provider-kubeswift to built-in providers
• cluster-api-provider-vsphere v1.17.0-beta.1: bump to CAPI v1.14.0-beta.1
• etcd v3.7.1: new patch release, see CHANGELOG; also v3.6.14, v3.5.33
• grpc v1.83.0: default to post-quantum cryptography in TLS key exchange
• nerdctl v2.3.5: bump bundled containerd to v2.3.3, BuildKit to v0.31.2, runc to v1.5.1

Shoutouts

• fabrizio.pandini: Shoutout to @Karthik-K-N for implementing a series of changes that reduce Cluster API E2E test duration by about 30 minutes, benefiting all Cluster API contributors.

• jberkus: Kudos to @Furkan AYDIN for helping us quickly move to the new inviter.co for this Slack and troubleshooting permission issues.