RepoJournal
Kubernetes @kubernetes
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-08-13
stories 79
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

KUBERNETES STEERING ELECTION OPENS VOTER REGISTRATION; KOPS CLEANUP BEGINS

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

my-git9 kubernetes-prow[bot] Peter Rifel reylejano shwetha-s-poojary bhope MAVRICK-1
8 people shipped this
my-git9 @my-git9 4 cited kubernetes-prow[bot] @kubernetes-prow[bot] 2 cited Peter Rifel @rifelpet 2 cited reylejano @reylejano 1 cited shwetha-s-poojary @shwetha-s-poojary 1 cited bhope @bhope 1 cited MAVRICK-1 @MAVRICK-1 reruno @reruno

The Kubernetes Steering Committee expanded eligible voters for the 2026 election to include all org members across five repositories, addressing a four-month data gap while maintainers pushed through test infrastructure and metrics refinements across the ecosystem.

The community governance move lands first: Kubernetes org members from kubernetes, kubernetes-sigs, kubernetes-client, kubernetes-csi, and etcd can now vote in the 2026 Steering Committee election [1], plugging the gap left by GitHub's contribution tracking blackout at the start of the year. Meanwhile, kops maintainers are systematically deprecating old patterns. The karpenter scenario now respects KOPS_EXTRA_FLAGS [2], and all 30 kops prow jobs switched from the deprecated KOPS_CONTROL_PLANE_SIZE to KOPS_CONTROL_PLANE_COUNT, which has been the standard since July 2023 [3]. Those changes ship today [4]. On the observability front, kube-state-metrics added kube_pod_status_disruption_reason, a metric that actually captures pods evicted through the Eviction API [5], closing a gap where the existing kube_pod_status_reason metric returned 0 for the most common disruption path. Documentation continues its steady sync: Chinese translations updated across resource definitions, API references, and feature gate documentation [6] [7] [8] [9] [10], while test-infra removed the unsupported CAPI release-1.11 job suite in favor of release-1.14 [11].

Action items

References

  1. [1] [Steering Election 2026]Add org members as eligible voters ↗ kubernetes/community
  2. [2] tests/e2e: honor KOPS_EXTRA_FLAGS in the karpenter scenario ↗ kubernetes/kops
  3. [3] kops: use KOPS_CONTROL_PLANE_COUNT and drop unused preset-e2e-platform-aws ↗ kubernetes/test-infra
  4. [4] Merge pull request #37674 from rifelpet/kops-cleanup-cp-count-and-dead-preset ↗ kubernetes/test-infra
  5. [5] feat: add kube_pod_status_disruption_reason metric ↗ kubernetes/kube-state-metrics
  6. [6] Merge pull request #56952 from lhpang-stack/agent/zh-cn-remove-hugepage-aware-eviction ↗ kubernetes/website
  7. [7] [zh-cn]sync resource-rule-v1-authorization ↗ kubernetes/website
  8. [8] [zh-cn]sync csi-changed-block-tracking-beta ↗ kubernetes/website
  9. [9] [zh-cn]sync labels-annotations-taints/_index ↗ kubernetes/website
  10. [10] [zh-cn]sync param-kind-v1-admissionregistration patch-v1-meta ↗ kubernetes/website
  11. [11] Remove CAPI release-1.11 jobs ↗ kubernetes/test-infra

$ ls kubernetes/reviews/ # the step-back reads

the week in review Kubernetes release v0.23.0 adds trixie kube-cross variant the month in review node-problem-detector 1.37.0 patches three CVEs
Full archive → Weekly reviews →

Quick answers

What shipped in Kubernetes on August 13, 2026?
The Kubernetes Steering Committee expanded eligible voters for the 2026 election to include all org members across five repositories, addressing a four-month data gap while maintainers pushed through test infrastructure and metrics refinements across the ecosystem. In total, 48 commits and 31 pull requests landed.
Who contributed to Kubernetes on August 13, 2026?
8 developers shipped this update, including kubernetes-prow[bot], my-git9, reylejano, MAVRICK-1, Peter Rifel, shwetha-s-poojary, reruno, and bhope.
What were the notable Kubernetes updates?
[Steering Election 2026]Add org members as eligible voters, tests/e2e: honor KOPS_EXTRA_FLAGS in the karpenter scenario, and kops: use KOPS_CONTROL_PLANE_COUNT and drop unused preset-e2e-platform-aws.
♥

$ log @kubernetes --recent

Control plane cleanups: watchcache context prep, RecursiveReadOnlyMounts gate removed 90 shipped Consistent get backed out when etcd transforms are on 121 shipped Admission webhook metrics go beta; watch cache gets a minheap freshness waiter 103 shipped ML-DSA support for service account tokens 7 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.