176 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-10-09
stories 52

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Per-release EC2 scale jobs, kops bastion capacity fallbacks

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

The day's real work is in CI plumbing: per-release EC2 scale-performance lanes, kops e2e bastions that survive EC2 capacity shortfalls, and a git-sync startup panic closed out.

Add per-release ec2 scale-performance-100 jobs kubernetes/test-infra

by dims

ci-kubernetes-e2e-ec2-scale-performance-100 now carries fork-per-release, with hand-forked jobs for release-1.36 (second cron tier, since that branch is already in the stable1 tier) and release-1.37. perf-dash picks the lanes up as aws-100Nodes-1.36 and aws-100Nodes-1.37, giving per-release kubelet and control-plane resource comparisons.

kubetest2: Give AWS e2e bastions instance-type fallbacks kubernetes/kops

by rifelpet

Over 60 days, 27 AWS kops e2e builds failed because EC2 had no capacity for an instance type in a single-AZ cluster's availability zone, and in every case the error named other AZs in the same region with capacity. The kubetest2 change gives e2e bastions instance-type fallbacks, so those runs stop failing on capacity alone.

Fix panic when git config contains a key without a value kubernetes/git-sync

by high-altitude-ai

git-sync could panic at startup when git config list -z returned a key with no value: the parser assumed every entry had a \n separator and indexed the second element unconditionally, but git emits such keys as key\0. Entries without a value are now handled explicitly and preserved in diagnostic output as null, distinct from an explicitly empty "".

Pin kops gce scale-performance-100 forks to release-branch CI builds kubernetes/test-infra

by Davanum Srinivas

The 1.36 and 1.37 forks of ci-kubernetes-e2e-gce-scale-performance-100 had been deploying master builds, because the kops scalability scenario reads K8S_VERSION rather than KUBERNETES_VERSION. K8S_VERSION is now set explicitly on the master job with a fork-per-release replacement, the forks point at ci/latest-1.36.txt and ci/latest-1.37.txt, and the unused KUBERNETES_VERSION is gone.

updates for Steering Committe elections 2026 kubernetes/community

by Priyankasaggu11929

Janet Kuo, Michael McCune, and Priyanka Saggu join the Steering Committee, while Antonio Ojea, Benjamin Elder, and Sascha Grunert move to Emeritus. Separately, the 2026 election's ballots.csv landed.

Quick answers

What shipped in Kubernetes on October 9, 2026?
The day's real work is in CI plumbing: per-release EC2 scale-performance lanes, kops e2e bastions that survive EC2 capacity shortfalls, and a git-sync startup panic closed out. In total, 35 commits and 17 pull requests landed.
Who contributed to Kubernetes on October 9, 2026?
7 developers shipped this update, including dims, hakman, kubernetes-prow[bot], rifelpet, high-altitude-ai, reylejano, and Priyankasaggu11929.
What were the notable Kubernetes updates?
Add per-release ec2 scale-performance-100 jobs, kubetest2: Give AWS e2e bastions instance-type fallbacks, and Fix panic when git config contains a key without a value.