Stay up-to-date on Kubernetes development in 15 minutes a week.
A new Kubernetes policy requires GitHub Actions workflows to pin actions using full 40-character commit SHAs instead of mutable references like latest or main. Non-compliant workflows will fail after April 15, 2026, so maintainers should update workflows and use Dependabot to keep them up to date, see details.
The default branch of the kubernetes/community repository has been renamed from master to main. Open PRs were automatically retargeted and existing /master/ links will continue to work, but contributors should update local branches and forks to stay aligned, see tracking issue.
SIG Release has updated platform support tiers and artifacts documentation with clearer, measurable criteria and a simplified structure, with no changes to supported platforms or artifacts, see PR.
A high-severity ingress-nginx vulnerability (CVE-2026-4342) enables configuration injection and potential code execution, affecting versions below v1.13.9, v1.14.5, and v1.15.1 as outlined in the issue. With ingress-nginx now EOL, users should upgrade and migrate.
Next Deadline: Docs Freeze, 9th April 2026
Code Freeze for v1.36 is now in effect. Enhancements that did not meet the freeze criteria have been removed from the milestone. Docs PRs and Release Highlights were due March 31, with Docs Freeze landing April 9 (AoE April 8).
Patch Releases
Kubernetes v1.36.0-beta.0, v1.35.3, v1.34.6, v1.33.10 were released last week, delivering the latest fixes and updates.
jrvaldes has promoted the NodeLogQuery feature to General Availability in Kubernetes v1.36 as part of KEP-2258: Node Log Query Enhancements. The PR was reviewed and approved by maintainers including liggitt and contributors from SIG Node and SIG Windows.
NodeLogQuery allows cluster administrators to retrieve node-level system and service logs directly through the Kubernetes API by proxying requests through the kubelet. Instead of logging into nodes with SSH or RDP and manually searching logs with tools such as journalctl or the Windows Event Viewer, operators can query logs with a single kubectl command.
The feature was originally introduced in Kubernetes 1.27 as an alpha capability and progressed to beta in Kubernetes 1.30 before graduating to GA in v1.36. During this time the implementation matured with improvements to filtering, cross-platform support for both Linux and Windows nodes, and security hardening after the discovery of CVE-2024-9042 affecting the Windows implementation.
Under the hood, the kubelet exposes a /logs/ HTTP endpoint that queries the operating system’s native logging infrastructure (journalctl on Linux and Get-WinEvent on Windows), allowing Kubernetes to provide a unified interface for retrieving node logs regardless of operating system.
The feature originated from work led by Aravindh Puthiyaparambil and contributors across SIG Windows and SIG Node. With the GA promotion, the NodeLogQuery feature gate is now locked to enabled, making node log queries a stable part of the Kubernetes debugging and observability toolkit.
KEP-4815: DRA: Add support for partitionable devices
This KEP restores the ability of Dynamic Resource Allocation (DRA) to support on-demand device partitioning within the newer “structured parameters” framework, enabling more efficient utilization of resources like GPUs and other accelerators. It introduces mechanisms for vendors to represent both full devices and overlapping partitions compactly, allowing the scheduler to safely allocate non-conflicting partitions while enabling dynamic creation of those partitions after allocation—without changing the existing user-facing ResourceClaim workflow.
The proposal is driven by use cases such as GPU partitioning, multi-host TPU scheduling, SR-IOV, and ensuring valid device topologies across single and multi-node environments, while also supporting logical devices composed of multiple physical resources.
The feature is currently under proposal stage, with ongoing discussions focused on restoring lost flexibility from “classic” DRA and aligning it with structured parameters, and is expected to evolve through standard Kubernetes release stages (alpha, beta, GA) based on implementation maturity and community feedback.
Unused condition on PersistentVolumeClaimStatus.MemoryQoS: memory.min for Guaranteed pods, memory.low for Burstable pods, with node-level metrics and rollback reconciliation (KEP-2570).preloadedImagesVerificationAllowlist in Kubelet’s configuration.PodGroupScheduled condition reflecting whether the group was successfully scheduled or is unschedulable.PodGroupPodsCount scheduler plugin to support workload-aware scheduling by prioritizing placements with higher pod counts within a group.RestartContainer on non-sidecar initContainers, as the resize of such containers has never been supported.ReconcilePoolWithName allows per-pool reconciliation without setting NodeName on slices.nf_conntrack_max to 1,048,576 to prevent excessive memory consumption on high-core machines when using automatic calculation.spec.resourceClaims field which can refer to ResourceClaims and ResourceClaimTemplates.StreamPodSandboxes, StreamContainers, StreamContainerStats, StreamPodSandboxStats, StreamPodSandboxMetrics) and New ImageService streaming RPC (StreamImages).DisruptionMode, PriorityClassName and Priority fields to Workload and PodGroup APIs to support workload-aware preemption when WorkloadAwarePreemption feature gate is enabled.UserNamespacesHostNetwork runtime handler and integrates the UserNamespacesHostNetworkSupport feature gate with the NodeDeclaredFeatures feature gate.DRAResourceClaimGranularStatusAuthorization feature gate is enabled (Beta in 1.36).PodReadyToStartContainers condition immediately after sandbox creation rather than after image pull, reducing the time to condition True.kubectl describe node now lists aggregated ResourceSlices when the ResourceSlice API is present, detailing slice name, driver, and pool.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.