Stay up-to-date on Kubernetes development in 15 minutes a week.
SIG Autoscaling has clarified its subproject donation requirements, formalizing what external projects need to satisfy to be adopted under the SIG.
Dims has published a post-Code-Freeze CI recovery writeup showing that contributors across SIGs fixed roughly 27 CI jobs through 60 PRs since July 22, with the sig-release-master-blocking board now green; the full gist lists about 30 open failing-test and flake issues that still need owners.
The KubeCon + CloudNativeCon NA 2026 schedule is now live.
Voting is now open for the 2026 Kubernetes Steering Committee election. Six candidates are running this year, including Sean McGinnis (stmcginnis), Michael McCune (elmiko), Priyanka Saggu (priyankasaggu11929), Janet Kuo (janetkuo), Kaslin Fields (kaslin), and Jack Francis (jackfrancis). Voting will remain open until October 1.
All current Kubernetes org members are eligible to vote this year due to GitHub contributions not being accurately tracked during the first four months of 2026. Members of the SRC or CoCC are also eligible. Eligibility can be checked at elections.k8s.io or in the full voter list in the election repository. If you believe you should be eligible, but are not, please file an exception.
Next Deadline: RC1 release, August 19
We are in the final stretch for v1.37, which looks like it’s going out on time. If you’re working on Release Notes or the blog you have plenty to do, but most contributors just need be ready to respond quickly to any test failures. This means you can start thinking about v1.38. Speaking of which, the v1.38 Shadow Application is already open, and due August 28th.
vshkrabkov fixed Pod event handling for updates where the Pod UID changes. Because a UID identifies a specific Pod instance, an update with a new UID represents a different Pod rather than a normal modification. Treating it as an ordinary update could leave consumers with stale state associated with the previous Pod. This PR represents the transition as a delete event for the old Pod followed by an add event for the new Pod, allowing API machinery and scheduling consumers to process the identity change correctly.
macsko fixed scheduler state tracking for Pods rejected during the PlacementFeasible stage. The scheduler uses UnschedulablePlugins to identify which plugins made a Pod unschedulable and which cluster events should cause it to be retried. This PR ensures that the relevant plugin information is recorded for PlacementFeasible rejections, improving requeue behavior for workload-aware scheduling and Dynamic Resource Allocation scenarios where placement can depend on device, resource, or topology changes.
This KEP proposes exposing device health information (such as GPU failures) in Pod Status so Kubernetes can indicate when a Pod is using a device that is unhealthy or has failed. Currently, device failures are difficult to diagnose because Pods often enter CrashLoopBackOff without any indication that the assigned device is the root cause, and Kubernetes may keep restarting the Pod on the same faulty device. By surfacing unhealthy devices directly in Pod Status, the proposal provides a generic mechanism for easier troubleshooting and better handling of temporary or permanent device failures, while keeping the initial scope small and extensible for future enhancements.
PodLevelResourceManagers is disabled by default.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.