The Wire · Showcase
KUBERNETES UNDEPRECATES LONG-LIVED FEATURE GATE AS API MACHINERY CLEANS HOUSE
By RepoJournal · Filed · About Kubernetes
The core Kubernetes project reversed a nine-year deprecation on enable-logs-handler while simultaneously purging locked GA feature gates from the API machinery, signaling a shift toward pragmatism over rigid deprecation timelines.
Kubernetes revived enable-logs-handler [1], an opt-in logging feature deprecated since 1.15 that remains actively used by production installers including GKE and Zalando's Kubernetes-on-AWS. The project acknowledged that after 20+ releases without removal, the feature has achieved de facto permanence — and that NodeLogQuery, the intended replacement, offers identical functionality with identical security posture. Simultaneously, sig-api-machinery landed sweeping cleanup: removal of locked GA feature gates [ref:2,ref:4] and redundant declarative minimums [ref:3,ref:5] that were cluttering the schema. Meanwhile, kops bumped etcd to v3.5.30 and v3.6.11 [ref:13,ref:14,ref:15], dropping support for the unmaintained 3.4 branch and refactoring the patch management system for faster future updates. Test infrastructure advanced with kubectl bumping ginkgo to v2.28.3 and gomega to v1.40.0 [ref:6,ref:7], while k8s.io image promotion pushed build and releng images across Go 1.25.10 and 1.26.3 variants [ref:20,ref:21,ref:22].
Action items
- → If running GKE or Zalando K8s-on-AWS: enable-logs-handler is staying. Plan accordingly in your log aggregation strategy. kubernetes/kubernetes [plan]
- → Review your kops deployments: etcd 3.4 support is dropped. Migrate to 3.5 or 3.6 before next cluster upgrade. kubernetes/kops [plan]
- → Update test dependencies if you maintain Kubernetes tooling: ginkgo v2.28.3 and gomega v1.40.0 now upstream standard. kubernetes/kubectl [monitor]
References
- [1] undeprecate enable-logs-handler kubernetes/kubernetes
- [2] Merge pull request #138907 from Jefftree/remove-locked-apimachinery-feature-gates kubernetes/kubernetes
- [3] Drop declarative minimum that is redundant with field type kubernetes/kubernetes
- [4] Remove locked GA feature gate ConsistentListFromCache kubernetes/kubernetes
- [5] Merge pull request #138921 from liggitt/drop-redundant-dv kubernetes/kubernetes
- [6] Merge pull request #138888 from pohly/ginkgo-gomega-update kubernetes/kubectl
- [7] dependencies: ginkgo v2.28.3, gomega v1.40.0 kubernetes/kubectl
- [8] etcd-manager: Bump etcd patches and drop 3.4 support ↗ kubernetes/kops
- [9] Merge pull request #18290 from hakman/bump-etcd kubernetes/kops
- [10] etcd-manager: drop support for etcd 3.4 kubernetes/kops
- [11] Image promotion for build-image v1.33.0-go1.25.10-bullseye.0 / v1.34.0-go1.25.10-bullseye.0 / v1.35.0-go1.25.10-bullseye.0 / v1.36.0-go1.26.3-bullseye.0 kubernetes/k8s.io
- [12] Image promotion for build-image v2.4.0-go1.26.3-bookworm.0 / v2.4.0-go1.25.10-bookworm.0 kubernetes/k8s.io
- [13] Image promotion for releng 1.26.3-trixie-0 / 1.25.10-trixie-0 kubernetes/k8s.io
FAQ
- What changed in Kubernetes on May 9, 2026?
- The core Kubernetes project reversed a nine-year deprecation on enable-logs-handler while simultaneously purging locked GA feature gates from the API machinery, signaling a shift toward pragmatism over rigid deprecation timelines.
- What should Kubernetes teams do about it?
- If running GKE or Zalando K8s-on-AWS: enable-logs-handler is staying. Plan accordingly in your log aggregation strategy. • Review your kops deployments: etcd 3.4 support is dropped. Migrate to 3.5 or 3.6 before next cluster upgrade. • Update test dependencies if you maintain Kubernetes tooling: ginkgo v2.28.3 and gomega v1.40.0 now upstream standard.
- Which Kubernetes repositories shipped on May 9, 2026?
- kubernetes/kubernetes, kubernetes/kubectl, kubernetes/kops, kubernetes/k8s.io