August Ships Kubernetes 1.37 RC and kOps 1.37 Beta

The month's center of gravity was release engineering. Kubernetes shipped v1.37.0-rc.1 [1], followed by a v1.37 snapshot after a pipeline fix that restored the .git exclusion [1]. kOps reached 1.37.0-beta.1 and made nodeup.xz canonical, part of a move that cut bootstrap downloads by 75% using xz-compressed nodeup . The release pipeline also shipped sigstore-go 1.2.1 and krel now signs attestations . Notably, a missing Go 1.26.5 image stalled patch builds for a day, illustrating how tightly the release train depends on image availability.

Security and permission hygiene dominated kOps. The project narrowed instance cloud permissions to actual consumers and narrowed instance describe permissions, reducing the blast radius of compromised credentials [2]. It plugged a DigitalOcean SSH key leak [3] and hardened IAM . kOps also killed kopeio, removed gossip leftovers, and dropped Calico grid jobs on GCE [4]. The docs now remove stale gossip guidance, and kOps cleans up remaining protokube service calls [5].

The autoscaler and ingress-GCE projects shed legacy code. Autoscaler removed cluster-autoscaler-core and dropped testing and reference providers that migrated to sigs.k8s.io [6]. Ingress-GCE addressed conflicting custom resources and allowed missing fields in a validation path [7].

Documentation and localization surged. The website published sneak peeks for v1.37 and gateway api v1.6, with Chinese locals following quickly [8]. Kubernetes docs flooded with Chinese and Korean translations, a trend that continued through the month. Meanwhile, test infrastructure fixed GCP flakes, hardened against config drift, and cut GPU waste by moving ci-kubernetes-cross-canary to the eks-prow-build-cluster [9].

Several ecosystem projects shipped targeted fixes. kubernetes-sigs/karpenter received validation updates, and minikube added a NodeProvisioner interface with linuxNodeProvisioner to refactor node provisioning [10]. kube-router modernized and kOps gated breaking changes. Metrics for 1.36 were published [11]. Across the board, the focus stayed on narrowing permissions, cutting waste, and clearing dead code as the 1.37 cycle matured.