Stay up-to-date on Kubernetes development in 15 minutes a week.
SIG-ContribEx will be managing all SIG/WG involvement in KubeCon NA this year, including Project Pavillion kiosks and onsite PR support for Kubernetes project groups. Interested SIGs, WGs, Committees, and Subprojects should apply using the form by July 19.
Next Tuesday’s monthly New Contributor Orientation features a SIG Docs-focused session. As the standalone SIG Docs New Contributor Orientation winds down, documentation-focused onboarding will continue through the monthly NCO. Join the session to learn how to get started contributing to Kubernetes documentation and how you can get involved with SIG Docs.
This month’s Steering Committee Meeting started out by discussing the 2026 Steering Committee Elections. Based on the feedback from last year’s election retro, we are starting the process earlier this year. Antonio Ojea, Benjamin Elder and Sascha Grunert will be stepping down this year and there will be 3 spots to be elected. One feedback from the steering committee was to announce the elections earlier before folks are out for their summer vacations. Keep a lookout for the steering committee elections anouncement soon!
The details of the Maintainer Summit was also discussed. The Maintainer Summit event will happen on the day before the colocated events and will only be happening at KubeCon EU and NA. If you want to have a booth in the project pavillion for a SIG or a subproject, you can request this via SIG ContribEx. The CFP announcement for the Maintainer Summit at KubeCon NA 2026 is not out yet, but is expected to be announced soon.
Next Deadline: Enhancements Freeze, 17th June 2026
Kubernetes v1.37 enters Enhancements Freeze on June 17th. Ensure all enhancement tracking issues, KEP requirements, and Production Readiness Review requirements are completed before the deadline.
June patch releases were targeted for June 9th for all supported Kubernetes versions.
In this pull request, yliaog promoted Dynamic Resource Allocation (DRA) Extended Resources to GA for the v1.37 milestone to establish a stable interface for managing specialized hardware accelerators. Driven and approved by contributors like pohly , liggitt , and bart0sh , the PR resolves tracking issue #138376 and aligns with the wg/device-management working group.
In this pull request, soltysh advanced a long-awaited capability by enabling the maxUnavailable rolling update strategy configuration by default for KEP-961. This change allows for tighter control over application availability and faster rollout tempos during workload updates without relying on manual feature gate activation.
adrianmoisey introduced a brand-new feature gate structurally isolating IPVS (IP Virtual Server) logic within kube-proxy for KEP-5495. This lays the crucial architectural groundwork for how the networking subsystem is managed, configured, and potentially decoupled in future releases, affecting both contributors modifying proxy code and users leveraging high-performance IPVS routing modes. Please test that this feature gate functions correctly in your networking setup.
EtcdRangeStream feature gate which initializes the watch cache via a single server-streaming etcd RangeStream RPC instead of paginated range requests, reducing apiserver memory pressure during bootstrap as part of KEP-5966.KubeProxyIPVS feature gate as Phase 2 of KEP-5495, gating IPVS mode in kube-proxy on an opt-in basis ahead of full removal in a future release.PublicKeysECDSA feature gate; users still on v1beta3 must migrate to v1beta4 before upgrading.WasFlushedFromUnschedulable after a flush event, causing them to be repeatedly re-evaluated.memory.high cgroup value, affecting memory-pressure behaviour for those workloads.memory.high on containers when MemoryQoS is disabled, preventing residual cgroup configuration when the feature is toggled off.test/e2e_node_windows, closing a long-standing Windows test coverage gap.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.