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-07-16
stories 100

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

KOPS 1.36 SHIPS WITH KUBERNETES 1.36 SUPPORT AND REWORKED ADDON MANAGEMENT

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

kOps 1.36.0 landed overnight with full Kubernetes 1.36 support, a fundamental overhaul of addon management, and the final chapter of the in-tree cloud provider deprecation.

The release [1] moves kops-channels from a standalone binary to a static pod on control-plane nodes, simplifying cluster bootstrapping and eliminating a deployment vector. Alongside this, three release artifacts crossed the finish line: kOps 1.35.2, 1.36.0, and 1.37.0-alpha.1 binary and container images are now promoted and ready for distribution [2][3]. The kOps team also shipped a major quality-of-life win in their release pipeline [4], parallelizing GitHub artifact uploads and adding SHA256 validation before promotion, which will cut release times and catch corrupted binaries before they ship. On the core Kubernetes side, the test suite is getting leaner [5][6][7] with the removal of unnecessary feature tags and provider-specific tests that were creating maintenance burden, while the API layer now supports full 32-bit unsigned Linux UIDs in container status [8], fixing a long-standing limitation for systems using high UID ranges. The infrastructure teams are also preparing for regional expansion with experimental Azure EUAP region E2E testing [9][10] and splitting resource-intensive node tests into faster and slower tracks to fix timeout issues [11].

Action items

References

  1. [1] v1.36.0 ↗ kubernetes/kops
  2. [2] Promote kOps 1.35.2, 1.36.0 and 1.37.0-alpha.1 binary artifacts ↗ kubernetes/k8s.io
  3. [3] Promote kOps 1.35.2, 1.36.0 and 1.37.0-alpha.1 images ↗ kubernetes/k8s.io
  4. [4] hack: parallelize GitHub release promotion and add checksum validation ↗ kubernetes/kops
  5. [5] Merge pull request #140542 from danwinship/ingress-no-feature kubernetes/kubernetes ↗
  6. [6] Merge pull request #140589 from borg-land/drop-reboot-test kubernetes/kubernetes ↗
  7. [7] Merge pull request #140529 from pohly/e2e-skip-if-provider-is kubernetes/kubernetes ↗
  8. [8] pkg/apis/core: allow uint32 Linux UIDs in container status (#138574) kubernetes/kubernetes ↗
  9. [9] feat(cloud-provider-azure): add experimental checkin for EUAP regions ↗ kubernetes/test-infra
  10. [10] Merge pull request #37480 from Liunardy/cloud-provider-azure-euap-checkin-fix-run ↗ kubernetes/test-infra
  11. [11] sig-node: split slow tests out of ci-kubernetes-node-e2e-containerd-alpha-features ↗ kubernetes/test-infra

Quick answers

What shipped in Kubernetes on July 16, 2026?
kOps 1.36.0 landed overnight with full Kubernetes 1.36 support, a fundamental overhaul of addon management, and the final chapter of the in-tree cloud provider deprecation. In total, 60 commits, 37 pull requests, and 3 releases landed.
Who contributed to Kubernetes on July 16, 2026?
9 developers shipped this update, including hakman, geewynn, kubernetes-prow[bot], upodroid, Liunardy, kannon92, moshevayner, and Kunalbehbud, and 1 more.
What were the notable Kubernetes updates?
v1.36.0, Promote kOps 1.35.2, 1.36.0 and 1.37.0-alpha.1 binary artifacts, and Promote kOps 1.35.2, 1.36.0 and 1.37.0-alpha.1 images.