The Wire · Showcase
KUBERNETES STEERING ELECTION OPENS VOTER REGISTRATION; KOPS CLEANUP BEGINS
By RepoJournal · Filed · About Kubernetes
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].
One email a day. Unsubscribe in one click.
Keep up with Kubernetes in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review kops e2e test changes if you maintain prow jobs or custom control plane sizing kubernetes/kops [plan]
- → Update scrape configs to use kube_pod_status_disruption_reason for eviction tracking kubernetes/kube-state-metrics [plan]
- → If you are an org member, verify your voter eligibility in the 2026 Steering election kubernetes/community [monitor]
References
- [1] [Steering Election 2026]Add org members as eligible voters ↗ kubernetes/community
- [2] tests/e2e: honor KOPS_EXTRA_FLAGS in the karpenter scenario ↗ kubernetes/kops
- [3] kops: use KOPS_CONTROL_PLANE_COUNT and drop unused preset-e2e-platform-aws ↗ kubernetes/test-infra
- [4] Merge pull request #37674 from rifelpet/kops-cleanup-cp-count-and-dead-preset kubernetes/test-infra
- [5] feat: add kube_pod_status_disruption_reason metric ↗ kubernetes/kube-state-metrics
- [6] Merge pull request #56952 from lhpang-stack/agent/zh-cn-remove-hugepage-aware-eviction kubernetes/website
- [7] [zh-cn]sync resource-rule-v1-authorization ↗ kubernetes/website
- [8] [zh-cn]sync csi-changed-block-tracking-beta ↗ kubernetes/website
- [9] [zh-cn]sync labels-annotations-taints/_index ↗ kubernetes/website
- [10] [zh-cn]sync param-kind-v1-admissionregistration patch-v1-meta ↗ kubernetes/website
- [11] Remove CAPI release-1.11 jobs ↗ kubernetes/test-infra