Stay up-to-date on Kubernetes development in 15 minutes a week.
Registration for Maintainer Summit EU 2026 is now open, and the full schedule is live. Register via: https://register.linuxfoundation.org/kccnc-eu-maintainer-summit-2026 . View the schedule at https://maintainersummiteu2026.sched.com and plan your day.
SIGs are asked to submit their annual reports by February 28, highlighting key accomplishments from the past year and identifying areas or subprojects that need additional support. Reports don’t have to be submitted by SIG/WG chairs, feel free to nominate candidates among your contributors.
KubeCon India CFP for Project Opportunities (Lightning Talks and Maintainer Track) is open, with submissions due by 1 March.
Open Source Summit India CFP closes on 4 March 2026. Submit your session here.
KubeCon Japan Regular CFP is open until 29 March 2026. Submit your proposal here.
Next Deadline: Feature blog freeze, 27th February 2026
Feature blog blurbs for v1.36 are due next week. Wrap up your submissions and get ready — Code Freeze is next.
Patch Releases 1.35.1, 1.34.4, 1.33.8, 1.32.12 were published last week, delivering the latest fix and updates.
This PR migrates validation of HorizontalPodAutoscalerSpec.MinReplicas to Kubernetes’ declarative validation framework with feature-gate awareness. It ensures validation dynamically respects the HPAScaleToZero feature gate, improving consistency, maintainability, and correctness of API validation as Kubernetes continues moving toward declarative validation.
This PR introduces the kubelet_metrics_provider metric to help users identify which metrics provider kubelet uses to expose container statistics. The metric improves observability and debugging capabilities and supports monitoring requirements from the CRI stats KEP.
KEP-4762: Allows setting arbitrary FQDN as the pod’s hostname
This proposal introduces a new hostnameOverride field in the podSpec that allows users to set any Fully Qualified Domain Name (FQDN) as a pod’s hostname. Once the API reaches GA, the Kubelet will always respect this field, bypassing the legacy behavior that derives hostnames from the hostname and subdomain fields and appends a cluster-specific suffix. By removing this restriction, pods can use exact FQDNs without automatic modification. The primary goal is to improve compatibility with traditional or legacy applications that rely on specific hostnames for authentication, authorization, or service logic. This change simplifies migration to Kubernetes by enabling strict DNS-based hostname matching required by some older systems.
This KEP graduated to beta in v1.35.
v2-alpha plugin output (Chart metadata, Notes.txt, dev Makefile targets), adds new project init options like --namespaced and --multigroup, and includes multiple CLI and e2e stability fixes.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.