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

SECRET VALIDATION OVERHAUL SHIPS AS RELEASE-1.32 WINDS DOWN

By RepoJournal · Filed · About Kubernetes

Kubernetes API just migrated Secret type validation to declarative rules while the release team drops 1.32 config and hardens build infrastructure with Go and gcloud updates.

The API desk shipped a major change to Secret immutability validation [1], wiring up declarative validation rules for the Secret type field and adding comprehensive test coverage for both CREATE flows and mutation cases. This is the kind of foundational work that makes validation safer and more maintainable across the board. Meanwhile, the release team is actively closing out the 1.32 cycle by dropping its release config [2] and pushing two critical infrastructure updates: Go has been bumped to 1.26.4/1.25.11 across k8s-cloud-builder and k8s-ci-builder [3], and gcloud SDK is pinned to 553.0.0 [4] to maintain Python 3.9 compatibility before the next version drops support entirely. The test infrastructure team is moving forward with CAPV testing for 9.1 v1alpha5 [5], expanding coverage as vSphere support matures. Documentation continues its localization push with Hindi translations for scheduling eviction [6] and Japanese style unification for driver terminology [7], while the website also landed a critical update to maxUnavailable StatefulSet docs [8] reflecting a feature gate that was disabled due to a recent bug fix.

Action items

References

  1. [1] Migrate secret type immutable (#136886) kubernetes/api
  2. [2] Merge pull request #37226 from cpanato/update-kubekins kubernetes/test-infra
  3. [3] Update k8s-cloud-builder and k8s-ci-builder to Go 1.26.4/1.25.11 ↗ kubernetes/release
  4. [4] Pin gcloud SDK to 553.0.0 for Python 3.9 compatibility kubernetes/release
  5. [5] CAPV: Add test for 9.1 v1alpha5 ↗ kubernetes/test-infra
  6. [6] Hindi Documentation | Intro for Scheduling Eviction ↗ kubernetes/website
  7. [7] [ja] Unify driver katakana notation ↗ kubernetes/website
  8. [8] KEP-961: update maxUnavailable docs to reflect the FG being off by default ↗ kubernetes/website

FAQ

What changed in Kubernetes on June 10, 2026?
Kubernetes API just migrated Secret type validation to declarative rules while the release team drops 1.32 config and hardens build infrastructure with Go and gcloud updates.
What should Kubernetes teams do about it?
Upgrade k8s-cloud-builder and k8s-ci-builder to Go 1.26.4/1.25.11 immediately • Pin gcloud SDK to 553.0.0 in your build environments before the next 554.0.0 release drops Python 3.9 support • Review Secret validation changes in your custom controllers if you have special immutability logic
Which Kubernetes repositories shipped on June 10, 2026?
kubernetes/api, kubernetes/test-infra, kubernetes/release, 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.