RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

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

The Wire · Showcase

APIMACHINERY 0.36.2 LANDS, AZURE CLOUD PROVIDER TESTS JUMP TO CAPZ MAIN

By RepoJournal · Filed · About Kubernetes

The core Kubernetes API machinery bumped a minor version while test infrastructure pivoted cloud-provider-azure's IPv6 and dual-stack jobs to an upstream fix not yet backported to release branches.

Kubernetes released apimachinery 0.36.2 [1] [2] with dependency updates that ripple across the entire ecosystem. Simultaneously, test-infra shifted cloud-provider-azure 1.30 and 1.31 presubmit jobs from CAPZ release-1.21 to main [3] [4] [5] to pick up a critical fix for IPv6 and dual-stack scenarios that hasn't landed in older release branches. This is a deliberate pivot: the team identified a blocker in CAPZ's release branch and made the call to test against bleeding-edge instead. Minikube pulled in Docker CLI 29.5.2 [7] [8] as a dependency bump, and there's an ongoing fix to ai-playground documentation around device resource allocation [6]. Website docs continue steady syncing across locales and spotlights.

Action items

References

  1. [1] Bump k8s.io/apimachinery from 0.36.1 to 0.36.2 in the all group ↗ kubernetes/release
  2. [2] Merge pull request #4435 from kubernetes/dependabot/go_modules/all-e2fab95551 kubernetes/release
  3. [3] chore: use capz main for cloud-provider-azure 1.30 and 1.31 presubmit versions for ipv6 and dualstack tests ↗ kubernetes/test-infra
  4. [4] Merge pull request #37251 from anndono/chengan/use-main-cloud-provider-azure-1.30-1.31-ipv6-dualstack kubernetes/test-infra
  5. [5] chore: use main for cloud-provider-azure 1.30 and 1.31 presubmit versions for ipv6 and dualstack tests kubernetes/test-infra
  6. [6] Fix ai-playground.md request limits to use the devices.es/dri ↗ kubernetes/minikube
  7. [7] Build(deps): Bump github.com/docker/cli from 29.4.1+incompatible to 29.5.2+incompatible ↗ kubernetes/minikube
  8. [8] Merge pull request #23095 from kubernetes/dependabot/go_modules/github.com/docker/cli-29.5.2incompatible kubernetes/minikube

FAQ

What changed in Kubernetes on June 15, 2026?
The core Kubernetes API machinery bumped a minor version while test infrastructure pivoted cloud-provider-azure's IPv6 and dual-stack jobs to an upstream fix not yet backported to release branches.
What should Kubernetes teams do about it?
Verify apimachinery 0.36.2 in your dependency tree and test locally before next release • Review CAPZ main branch behavior in your Azure test runs if you're using cloud-provider-azure 1.30 or 1.31 • Check minikube changelog for Docker CLI 29.5.2 changes if you run local dev clusters
Which Kubernetes repositories shipped on June 15, 2026?
kubernetes/release, kubernetes/test-infra, kubernetes/minikube

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.