RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

  1. Mon 4 may
  2. Tue 5 may
  3. Wed 6 may
  4. Thu 7 may
  5. Fri 8 may
  6. Sat 9 may
  7. Sun 10 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

KOPS SHEDS BLOAT: HELM AND GCP DEPENDENCIES GONE

By RepoJournal · Filed · About Kubernetes

kOps just dropped two massive dependency chains it barely used — cutting 43k lines of vendored code and simplifying its cloud provider story.

The kOps team eliminated `helm.sh/helm/v3` entirely after discovering `toolbox template` only needed two narrow APIs from it [1]. That single module was pulling in containerd, oras-go, and most of helm's chart machinery with zero benefit. In the same sweep, they forked a single OAuth2 helper function out of `k8s.io/cloud-provider-gcp` [2], which had been dragging in the entire GCE cloud provider, GoogleCloudPlatform SDKs, and alpha/beta compute APIs kOps never touched. Separately, Azure blob storage URLs got redesigned to be self-contained [3] — the storage account name now lives in the URL itself rather than an environment variable, forcing a clean migration path and eliminating environment-dependent state. On the upgrade front, kOps bumped the AWS load balancer controller to 3.3.0 [4] specifically to fix failing prow jobs, and switched structured-merge-diff from v4 to v6 [5]. Meanwhile, the Kubernetes core repo is in cleanup mode: dropping the LogarithmicScaleDown feature gate after 1.31 GA [6], removing NodeLocalCRISocket from kubeadm in 1.37 [7], and replacing deprecated `wait.PollImmediate` calls across the test suite [8].

Action items

References

  1. [1] chore: drop helm dependency and fork strvals ↗ kubernetes/kops
  2. [2] chore: drop cloud-provider-gcp dependency and fork NewAltTokenSource ↗ kubernetes/kops
  3. [3] azure: encode storage account in azureblob:// URLs ↗ kubernetes/kops
  4. [4] Upgrade AWS load balancer controller to 3.3.0 ↗ kubernetes/kops
  5. [5] chore: switch structured-merge-diff from v4 to v6 ↗ kubernetes/kops
  6. [6] Merge pull request #138711 from soltysh/drop_LogarithmicScaleDown kubernetes/kubernetes
  7. [7] Merge pull request #138645 from neolit123/1.37-remove-the-NodeLocalCRISocket-fg kubernetes/kubernetes
  8. [8] Merge pull request #138777 from Jefftree/fix-pollimmediate-deprecated kubernetes/kubernetes

FAQ

What changed in Kubernetes on May 6, 2026?
kOps just dropped two massive dependency chains it barely used — cutting 43k lines of vendored code and simplifying its cloud provider story.
What should Kubernetes teams do about it?
Review kOps dependency chain if you vendor it — 43k lines of unused code just left the building • Plan Azure blob URL migration before next kOps upgrade — environment variable support is gone • Update AWS load balancer controller in your kOps clusters to 3.3.0
Which Kubernetes repositories shipped on May 6, 2026?
kubernetes/kops, kubernetes/kubernetes

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.