Week Ending May 18, 2025

Developer News

James Sturtevant and Amim Knabben are stepping down from their roles as techincal leads in SIG Windows and Yuanliang Zhang is notimated as the new Lead

Wenjia Zhang has stepped down as the co-chair of Kubernetes SIG etcd. Siyuan Zhang is nominated to take over Wenjia’s role as the co-chair.

SIG Contributor Experience has updated the help-wanted guidelines to remove the “low barrier to entry” requirement. This improves the distinction between “good first issue” and “help-wanted” and better aligns with other open source projects. The help-wanted issues still require clear tasks, goldilocks priority and must be up-to-date.

Release Schedule

Next Deadline: v1.34 cycle starts May 19

The v1.34 release cycle has officially started this week, with a planned release date of 27th August.

Patch releases v1.33.1, 1.32.5, 1.31.9 and 1.30.13 are available. This is mostly a bugfix release, with a golang update.

Featured PRs

131299: DRA: prevent admin access claims from getting duplicate devices

This PR fixes a bug where ResourceClaims with adminAccess could be allocated the same device multiple times within a single claim; The DRA allocator now checks that each device is used only once per claim, preventing invalid CDI specs and ensuring correct behavior for device sharing with Dynamic Resource Allocation.

131345: scheduler: return UnschedulableAndUnresolvable when node capacity is insufficient

This PR updates the NodeResourcesFit plugin to return UnschedulableAndUnresolvable when a pod’s resource requests exceed a node’s allocatable capacity, even if the node is empty; This avoids unnecessary preemption attempts for nodes that can never satisfy the request, improves scheduling efficiency in large clusters, and provides clearer signals for unschedulable pods.

KEP of the Week

KEP 4247: Per-plugin callback functions for efficient requeueing in the scheduling queue

This KEP introduced the QueueingHint functionality to the Kubernetes scheduler, enabling plugins to provide more precise suggestions for when to requeue Pods. By filtering out low-impact events such as unnecessary Node updates for NodeAffinity the scheduler reduced redundant retries and improved scheduling throughput. The KEP also allowed plugins like the DRA plugin to skip backoff in specific cases, enhancing performance for Pods requiring dynamic resource allocation by avoiding unnecessary delays while waiting for device driver updates.

This KEP is tracked for beta in v1.34.

Other Merges

e2e tests for kuberc added
Scheduler improved the backoff calculation to O(1)
Response body closed after http calls in watch test
Error message improved when a pod with user namespaces is created and the runtime doesn’t support user namespaces
DRA: Reject NodePrepareResources if the cached claim UID doesn’t match resource claim
suggestChangeEmulationVersion to clarify how to test a locked feature for emulation version
kubelet removed the deprecated –cloud-config flag
Non-scheduling related errors to not lengthen the Pod scheduling backoff time
kube-log-runner adds log rotation
Scheduler introduced pInfo.GatingPlugin to filter out events more generally

Subprojects and Dependency Updates

etcd releases v3.6.0 bringing bugfixes and features like robust downgrade support, full migration to the v3store backend, Kubernetes-style feature gates, major memory optimizations and new health check endpoints for improved cluster monitoring.

Shoutouts

Josh Berkus (@jberkus): A big TY to Benjamin Wang (@Benjamin Wang) and Wenjia Zhang (@wenjiaswe) for getting Etcd 3.6 out the door, and to Tim Bannister (@LMKTFY), Ryota Sawada (@Ryota), Mario Fahlandt (@Mario Fahlandt) and Kaslin Fields (@kaslin) for helping promote it!

Last Week In Kubernetes Development (LWKD) is a product of multiple contributors participating in Kubernetes SIG Contributor Experience. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.

You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.