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 9, 2025

Developer News

The next New Contributor Orientation will be March 18. Scripts for the NCO are complete, so if you’d be willing to run one someday, please contact SIG-ContribEx.

SIG/WG Leads, please finish your 2024 annual reports if you have not already.

KubeCon London Reminders: Meet & Greet and register for the Maintainer Summit

Release Schedule

Next Deadline: Code Freeze, March 20

Exceptions are closed, and we are on the countdown to Code Freeze, plus many other deadlines.

Patch releases 1.29.15, 1.30.11, 1.31.7, and 1.32.3 are available.

KEP of the Week

KEP 4960: Container Stop Signals

This KEP aims to add the container runtime level STOPSIGNAL instruction to the Kubernetes API. The KEP proposes adding a StopSignal container lifecycle which takes a valid signal which would be sent to the container runtime when the container is stopped. Currently the only way to configure custom stop signals is to bake them in the container image definition. This is difficult if you are using third party images. Container runtimes today reads the stop signal defined in container images and if there is none defined, falls back to SIGTERM. The new StopSignal lifecycle would have a higher priority than both of these. If a container has a stop signal defined in the container spec, that signal would be used over the signal defined in the image. The stop signal would get the default value of SIGTERM if no signal is defined in either the container spec or in the image definition.

This KEP is tracked for alpha in the ongoing 1.33 release cycle.

Other Merges

Promotions

Deprecated

Subprojects and Dependency Updates

Shoutouts

No shoutouts this week. Want to thank someone for special efforts to improve Kubernetes? Tag them #shoutouts channel.

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.