Who contributed to Kubernetes on May 16, 2026?

4 developers shipped this update, including hakman, rrangith, adrianmoisey, and mm4tt.

What were the notable Kubernetes updates?

Remove the unused in-tree cloud config, Remove the unused in-tree cloud config, and Merge pull request #18347 from hakman/drop-in-tree-cloud.config.

@kubernetes

Container orchestration - what platform teams ship on

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

KOPS DROPS IN-TREE CLOUD CONFIG, AZURE SHIFTS TO SECRETS

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

4 people shipped this

hakman @hakman 2 cited

rrangith @rrangith 1 cited

adrianmoisey @adrianmoisey 1 cited

mm4tt @mm4tt 1 cited

kOps is gutting years of cloud configuration cruft, moving Azure cloud-config from per-node files to a cluster-managed Secret while deprecating the unused in-tree cloud provider flag that's been dead code since Kubernetes 1.31.

The kOps team completed a three-PR cleanout of the in-tree cloud-provider path [1][2][3]. Since kOps enforces --cloud-provider=external across all clouds and versions 1.31+, the entire --cloud-config flag and the azure.json file it pointed to have been no-ops. Meanwhile, the Azure cloud-controller-manager now reads configuration from a Kubernetes Secret instead [4], matching upstream Helm chart conventions and giving operators a single cluster-managed object rather than managing per-node files through nodeup. The related Azure nodeup config fields are being trimmed [5], reducing surface area. In parallel, the Cluster Autoscaler is making smarter resource decisions: it now respects per-group resource quotas during scale-up balancing [6], fixing a bug where groups could exceed their quota limits. The autoscaler also shipped memory optimizations by stripping managed fields from informer caches [7][8], a win for large clusters, and added observedGeneration to VPA status for standardized condition tracking [9]. The Scheduler fixed pod group preemption behavior to match preemptor eligibility rules [10], and kubeadm now warns users who've configured kube-proxy with the deprecated IPVS mode [11], pushing them toward nftables (GA since 1.33) or legacy iptables on older kernels.

Action items

→ If running kOps on Azure: upgrade to consume cloud-config from Secret instead of azure.json files kubernetes/kops [plan]
→ Review your kube-proxy configuration if you've set mode: ipvs and plan a migration path to nftables or iptables kubernetes/kubernetes [plan]
→ Enable Scale Up Salvo in Cluster Autoscaler if you run large unschedulable pod queues (flag currently false by default) kubernetes/autoscaler [monitor]
→ Verify your Cluster Autoscaler respects resource quotas during multi-group scale-ups after upgrading kubernetes/autoscaler [immediate]

References

[1] Remove the unused in-tree cloud config ↗ kubernetes/kops
[2] Remove the unused in-tree cloud config kubernetes/kops
[3] Merge pull request #18347 from hakman/drop-in-tree-cloud.config kubernetes/kops
[4] azure: load cloud config from a Secret instead of azure.json ↗ kubernetes/kops
[5] azure: remove unused cloud config fields from nodeup config kubernetes/kops
[6] fix: respect resource quotas when balancing similar nodegroups ↗ kubernetes/autoscaler
[7] Strip managed fields from informer caches to reduce memory kubernetes/autoscaler
[8] Merge pull request #9634 from adrianmoisey/remove-managed-fields kubernetes/autoscaler
[9] VPA: Add observedGeneration to status and conditions ↗ kubernetes/autoscaler
[10] scheduler: match preemptor eligibility behavior in pod group preemption ↗ kubernetes/kubernetes
[11] kubeadm: warn if the user has configured kube-proxy with 'ipvs' kubernetes/kubernetes

Quick answers

What shipped in Kubernetes on May 16, 2026?: kOps is gutting years of cloud configuration cruft, moving Azure cloud-config from per-node files to a cluster-managed Secret while deprecating the unused in-tree cloud provider flag that's been dead code since Kubernetes 1.31. In total, 55 commits and 33 pull requests landed.
Who contributed to Kubernetes on May 16, 2026?: 4 developers shipped this update, including hakman, rrangith, adrianmoisey, and mm4tt.
What were the notable Kubernetes updates?: Remove the unused in-tree cloud config, Remove the unused in-tree cloud config, and Merge pull request #18347 from hakman/drop-in-tree-cloud.config.

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 10 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 10 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.