139 wires and counting

$ follow Kubernetes

Keep up with Kubernetes in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-16
stories 88

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

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

By RepoJournal · Filed · About Kubernetes · Composed from the cited sources · methodology

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

References

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