LWKD logo

Last Week in Kubernetes Development

Stay up-to-date on Kubernetes development in 15 minutes a week.

Subscribe
Mastodon
BlueSky
RSS

View LWKD on GitHub

Week Ending March 8, 2026

Developer News

Next Tuesday is the monthly New Contributor Orientation. Join at one of two times to learn all about starting your contribution journey.

SIG Testing chair Brian McQueen moved to emeritus due to lack of recent activity. Thank you Brian McQueen for helping lead SIG Testing and for his contributions to the community.

We are hosting the Kubernetes Meet & Greet for Wednesday March 25th lunch at Kubecon Europe. Kubernetes contributors, as well as people interested in becoming contributors, should join us.

Release Schedule

Next Deadline: Code & Test Freeze, 19th March 2026

We’re heading into Code & Test Freeze for v1.36 next week. Make sure your feature work is wrapped up and merged before the deadline. After the freeze, only critical fixes land, and anything else will need an exception.

The March Kubernetes patch releases are delayed and now expected early next week. The cherry-pick deadline has been extended to Friday, March 13 at 5 PM PT.

#136976: Create Workload API v1alpha2

Introduces scheduling.k8s.io/v1alpha2 Workload and PodGroup APIs as part of ongoing workload-aware scheduling work. This replaces the previous v1alpha1 Workload API and updates Pods to reference scheduling groups through a new SchedulingGroup field, decoupling PodGroups from Workloads and enabling more flexible workload-level scheduling.

KEP of the Week

KEP-4828: Component Flagz

This proposal aims to improve observability, troubleshooting, and debugging for core Kubernetes components by introducing a flagz endpoint for each component. The endpoint would expose the command-line flags used to start a component, giving users real-time visibility into its active configuration and helping diagnose misconfigurations or unexpected behavior. Building on ideas from the Component Statusz KEP but introducing a dedicated endpoint, the flagz interface would allow users to dynamically inspect and understand the flags currently applied to running Kubernetes components, making it easier to detect configuration issues that could lead to instability or outages. However, the proposal does not intend to replace existing monitoring mechanisms such as metrics, logs, or traces, nor does it aim to provide information about components that are inaccessible due to network restrictions.

This KEP graduated to alpha in v1.35.

Other Merges

Promotions

Deprecated

Version Updates

Subprojects and Dependency Updates

Shoutouts

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.