Last Week In Kubernetes Development

Archives
April 9, 2026

LWKD: Week Ending April 05, 2026

Week Ending April 05, 2026

Developer News

The NVIDIA DRA Driver for GPUs has been officially onboarded as a SIG Node subproject in kubernetes-sigs, formally moving community governance of the GPU DRA driver that NVIDIA donated at the 2026 KubeCon+CloudNativeCon EU into upstream Kubernetes.

A CPU DRA Driver v0.1.0 has been released, enabling exclusive CPU pinning for workloads via the DRA framework with support for aligning CPU allocations with other DRA-managed resources such as NICs and GPUs.

The Kubernetes contributor guide has been updated with a new AI usage and disclosure policy; all contributors should review the changes before using AI tools in their Kubernetes contributions.

The ingress-nginx and ingate Slack channels have been archived following the project's retirement in March; contributors should migrate to #gateway-api or other relevant channels.

Steering Committee Meeting

The Kubernetes Steering Committee will move all Kubernetes meeting management to the LFX Platform to address broken invites and limited access for subproject leads. The system centralizes scheduling, enables subprojects to manage meetings, and syncs with the Kubernetes calendar. Community leads will be required to create LFX accounts.

Steering added mandatory requirements to the Kubernetes AI policy. Contributors must disclose AI usage in pull requests. AI tools cannot be listed as co-authors or co-sign PRs due to Linux Foundation legal restrictions. Also, do not add mentions like “assisted by AI” in commit trailers, to prevent third-party marketing misuse.

The GitHub Admin Team introduced a per-repo opt-in policy for AI code review tools. It defines the lifecycle: request, security review, 90-day trial, and evaluation. Please review and provide feedback.

To improve onboarding, ContribEx will replace the current NCO presentations with a SIG-focused format, as they were too general. This updated approach aims to make sessions more relevant and actionable, with SIG leads playing a key role in delivering them.

Release Schedule

Next Deadline: Docs Freeze, 9th April 2026

We’re heading into Docs Freeze for v1.36, landing April 9. The release-1.36 branch will be created alongside Docs Freeze, marking the final stages of the release cycle.

Cherry-picks for the next round of patch releases are due April 10.

KEP of the Week

KEP-5075: DRA Consumable Capacity

This KEP introduces support for consumable capacity in Dynamic Resource Allocation (DRA), enabling multiple independent resource claims to allocate and share portions of the same underlying device. Unlike the traditional exclusive allocation model, this approach allows efficient device sharing across unrelated pods and namespaces while ensuring that total allocated capacity remains within device limits through a scheduler-enforced consumable capacity model.

This approach supports shared network devices via CNI, virtual GPU memory allocation, and other multi-allocatable devices. It introduces mechanisms for capacity-aware scheduling, per-request capacity requirements, consumed capacity tracking, and safeguards to prevent unintended duplicate allocations within a single claim.

The feature became alpha in Kubernetes 1.34 should become beta in 1.36.

Other Merges

  • Introducing fine-grained authorization checks for Dynamic Resource Allocation (DRA) ResourceClaim status updates.
  • Add the UserNamespacesHostNetwork runtime handler and integrates the UserNamespacesHostNetworkSupport feature gate with the NodeDeclaredFeatures feature gate.
  • Fix kubelet to preserve DRA NodeAllocatableResourceClaimStatuses in Pod.Status.
  • Fix erroneously reporting a pod-level resize in progress on pod creation when InPlacePodLevelResourcesVerticalScaling is enabled.

Version Updates

  • cdi spec to 0.5.0

Subprojects and Dependency Updates

  • cluster-api v1.13.0-rc.0: bumps to Go 1.25, controller-runtime v0.23, and k8s.io/* v0.35; improves KCP failure recovery and controller memory footprint; removes v1alpha3 and v1alpha4 apiVersions; also v1.12.5, v1.11.8
  • cluster-api-provider-vsphere v1.16.0-rc.0: bumps to CAPI v1.13.0-rc.0; adds v1beta2 API support for govmomi and supervisor; enables priority queue and rate limiting by default; removes v1alpha3 and v1alpha4 apiVersions
  • prometheus v3.11.1: fixes startup failure for OTLP HTTP tracing with insecure mode

Shoutouts

  • No shoutouts this week. Want to thank someone for special efforts to improve Kubernetes? Tag them in the #shoutouts channel.
Don't miss what's next. Subscribe to Last Week In Kubernetes Development:
Powered by Buttondown, the easiest way to start and grow your newsletter.