Who contributed to Kubernetes on May 11, 2026?

5 developers shipped this update, including rifelpet, hakman, silvery1622, pacoxu, and saschagrunert.

What were the notable Kubernetes updates?

aws: Only set nodeAllocatableUpdatePeriodSeconds on K8s 1.35+, e2e: add upgrade test for gossip, and dns-controller: make priorityClassName configurable.

@kubernetes

Container orchestration - what platform teams ship on

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

KOPS LOCKS DOWN K8S 1.35 COMPATIBILITY WHILE VSPHERE ADDS MULTI-API SUPPORT

By RepoJournal · Filed 06:01 UTC on May 11, 2026 · About Kubernetes

5 people shipped this

hakman @hakman 2 cited

silvery1622 @silvery1622 2 cited

rifelpet @rifelpet 1 cited

pacoxu @pacoxu 1 cited

saschagrunert @saschagrunert 1 cited

Kops shipped critical version gating for a CSI feature that was breaking cluster validation on older Kubernetes releases, while the vSphere cloud provider decoupled itself from API versioning to support multiple VM Operator versions simultaneously.

Kops merged a fix [1] that prevents nodeAllocatableUpdatePeriodSeconds from being set on Kubernetes versions below 1.35, where the underlying MutableCSINodeAllocatableCount feature gate doesn't exist by default — this was causing validation failures across clusters. In parallel, the team landed upgrade e2e tests for gossip [2], exposing gaps in Azure and GCE implementations that need attention before the feature stabilizes across cloud providers. The dns-controller now accepts a configurable priorityClassName [3] instead of hardcoding system-cluster-critical, giving operators control during upgrades when old and new images run side-by-side. Over in vSphere, cloud-provider-vsphere introduced a Hub Type abstraction layer [4] that decouples business logic from specific VM Operator API versions, with v1alpha6 support now landed [5] alongside backward compatibility for v1alpha2 and v1alpha5 — this is the pattern that lets infrastructure providers stop chasing API versions. Kubernetes core merged two test stability fixes: one for PodGroup protection flakes [6] and another [7] forcing block I/O writes through the kernel instead of page cache, making cadvisor metrics reliable in test environments.

Action items

→ If running kops on K8s <1.35, upgrade kops immediately to pick up CSI feature gating fix kubernetes/kops [immediate]
→ Review GCE gossip bootstrap configuration — worker IPs not propagating correctly [ref:2] kubernetes/kops [plan]
→ If managing vSphere clusters, test VM Operator API version flag for your upgrade path kubernetes/cloud-provider-vsphere [plan]
→ Monitor container metrics tests — block I/O flakes should drop with latest kubernetes merge kubernetes/kubernetes [monitor]

References

[1] aws: Only set nodeAllocatableUpdatePeriodSeconds on K8s 1.35+ ↗ kubernetes/kops
[2] e2e: add upgrade test for gossip ↗ kubernetes/kops
[3] dns-controller: make priorityClassName configurable ↗ kubernetes/kops
[4] ✨ vsphereparavirtual: Support multiple VM Operator API versions ↗ kubernetes/cloud-provider-vsphere
[5] ✨ vsphereparavirtual: add support for VM Operator API version v1alpha6 ↗ kubernetes/cloud-provider-vsphere
[6] fix PodGroup protection test flake by waiting for pod watch before delete ↗ kubernetes/kubernetes
[7] Fix ContainerMetrics cadvisor test flake for block I/O metrics ↗ kubernetes/kubernetes

Quick answers

What shipped in Kubernetes on May 11, 2026?: Kops shipped critical version gating for a CSI feature that was breaking cluster validation on older Kubernetes releases, while the vSphere cloud provider decoupled itself from API versioning to support multiple VM Operator versions simultaneously. In total, 24 commits and 17 pull requests landed.
Who contributed to Kubernetes on May 11, 2026?: 5 developers shipped this update, including rifelpet, hakman, silvery1622, pacoxu, and saschagrunert.
What were the notable Kubernetes updates?: aws: Only set nodeAllocatableUpdatePeriodSeconds on K8s 1.35+, e2e: add upgrade test for gossip, and dns-controller: make priorityClassName configurable.

SCHEDULER GAINS PREQUEUING FILTER, KUBELET USER NAMESPACES MOVE TO BETA

Kubernetes tackles the pod requeue bottleneck that's been choking large clusters, while user namespacing ships closer to production.

go 19 shipped 1-min read

@kubernetes 1 day ago

CLUSTER-AUTOSCALER PATCHES HIT ALL RELEASE BRANCHES AS DRA AND VOLUMEMOUNT BIND OPTIONS LAND

Cluster-autoscaler shipped four patch releases across versions 1.33 through 1.36 fixing ProvisioningRequest condition application and Scaleway node detection, while Kubernetes core merged DRA node operations and volumeMount bind mount options.

go 89 shipped 1-min read

@kubernetes 2 days ago

DRA GETS SMARTER RESOURCE ACCOUNTING, CLUSTER-AUTOSCALER ROLLS OUT FOUR PATCHES

Dynamic Resource Allocation fixed device accounting across its resource pool controller while cluster-autoscaler shipped maintenance releases across four versions.

go 52 shipped 1-min read

@kubernetes 3 days ago

DRA GRADUATES TO STABLE, KUBELET METRICS BYPASS CADVISOR, NAMESPACE LIFECYCLE UNBLOCKED

Three critical production fixes ship across core scheduler, metrics, and admission layers while DRA resource tracking stabilizes after surfacing a crash bug in the informer.

go 129 shipped 1-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.