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

K8S 0.35.5 ROLLS ACROSS THE STACK

By RepoJournal · Filed · About Kubernetes

Kubernetes 0.35.5 is propagating through core dependencies across node-problem-detector, cloud-provider-vsphere, and test infrastructure, along with a batch of routine security and testing updates.

The k8s.io/api and k8s.io/client-go bump to 0.35.5 [1] is moving through node-problem-detector, where it pairs with updates to apimachinery and component-base across test directories. Cloud-provider-vsphere is tracking the same 0.35.5 release in its test e2e suite [4], signaling coordinated API surface changes worth watching. Test infrastructure added 1.36 e2e tests for kueue [2] and rolled test-infra base images to Alpine 3.20 [3] to resolve Python version conflicts in gcloud tooling. The vsphere provider also bumped golang.org/x/net to 0.55.0 and ginkgo/v2 to 2.29.0 [5], the latter introducing GinkgoHelperGo for better goroutine test handling. Documentation sync continues across Korean, Chinese, and French localization branches [6], [7], [8], typical housekeeping that won't block production workloads.

Action items

References

  1. [1] chore(deps): bump the k8s group across 2 directories with 4 updates ↗ kubernetes/node-problem-detector
  2. [2] add 1-36 e2e tests for kueue ↗ kubernetes/test-infra
  3. [3] triage: bump alpine base image to 3.20 ↗ kubernetes/test-infra
  4. [4] :seedling: (chore): Bump the kubernetes group in /test/e2e with 3 updates ↗ kubernetes/cloud-provider-vsphere
  5. [5] :seedling: (chore): Bump github.com/onsi/ginkgo/v2 from 2.28.3 to 2.29.0 in /hack/tools ↗ kubernetes/cloud-provider-vsphere
  6. [6] [ko] Sync ko container runtimes doc with English source ↗ kubernetes/website
  7. [7] [zh-cn]sync kube-scheduler ↗ kubernetes/website
  8. [8] [fr] : Added translation of the container runtimes ↗ kubernetes/website

FAQ

What changed in Kubernetes on May 26, 2026?
Kubernetes 0.35.5 is propagating through core dependencies across node-problem-detector, cloud-provider-vsphere, and test infrastructure, along with a batch of routine security and testing updates.
What should Kubernetes teams do about it?
Review k8s.io/api 0.35.5 changes in node-problem-detector and cloud-provider-vsphere for breaking API surface shifts • Monitor 1.36 e2e kueue tests for stability before 1.36 release • Verify Alpine 3.20 base image compatibility with gcloud in your CI pipelines
Which Kubernetes repositories shipped on May 26, 2026?
kubernetes/node-problem-detector, kubernetes/test-infra, kubernetes/cloud-provider-vsphere, kubernetes/website

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.