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-12
stories 50

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

GCP CLOUD PROVIDER ROLLBACK REVEALS RBAC REGRESSION—NODE DELETION BROKEN IN GKE

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

The cloud-provider-gcp team reverted a critical library update after discovering it broke node lifecycle permissions, leaving orphaned GCE instances stranded in clusters.

A v1.34.0 library bump [1] shipped yesterday but was reverted within hours [2] after exposing a cascading permission failure. The root cause: NodeLifecycleController was using a hardcoded client identity instead of respecting configured RBAC roles, preventing nodes from being deleted after their backing GCE instances vanished [3]. This regression was introduced by an earlier permission refactor [3], so the team is now carefully unwinding that work. In parallel, the cluster directory removal [4] continues as planned—kubetest2-gce dependency is gone, so that testing infrastructure is being cleaned up. Meanwhile, test-infra is tightening its own house: 14 periodic jobs with zero green builds in 90+ days are getting axed [5], and Windows Azure tests are coming back online after a capz provider fix [6].

Action items

References

  1. [1] Update GoogleCloudPlatform/k8s-cloud-provider to v1.34.0 ↗ kubernetes/cloud-provider-gcp
  2. [2] Revert "Update GoogleCloudPlatform/k8s-cloud-provider to v1.34.0" ↗ kubernetes/cloud-provider-gcp
  3. [3] fix: Ensure NodeLifecycleController has correct permissions (#1118) ↗ kubernetes/cloud-provider-gcp
  4. [4] Remove the cluster directory ↗ kubernetes/cloud-provider-gcp
  5. [5] config/jobs: delete 14 periodics with no green build in 90+ days ↗ kubernetes/test-infra
  6. [6] test(cloud-provider-azure): re-add Windows periodic jobs after capz fix ↗ kubernetes/test-infra

Quick answers

What shipped in Kubernetes on May 12, 2026?
The cloud-provider-gcp team reverted a critical library update after discovering it broke node lifecycle permissions, leaving orphaned GCE instances stranded in clusters. In total, 32 commits and 18 pull requests landed.
Who contributed to Kubernetes on May 12, 2026?
4 developers shipped this update, including cheftako, hdp617, dims, and Liunardy.
What were the notable Kubernetes updates?
Update GoogleCloudPlatform/k8s-cloud-provider to v1.34.0, Revert "Update GoogleCloudPlatform/k8s-cloud-provider to v1.34.0", and fix: Ensure NodeLifecycleController has correct permissions (#1118).