Originally published on kuryzhev.cloud
A platform team has a Friday maintenance window, a cluster still on 1.36, and a ticket that says "get us on current before the next audit." Planning the Kubernetes 1.37 upgrade is mostly about finding the three or four things in your cluster that the new minor version can break, not about the headline features.
Kubernetes 1.37 was released on 2026-08-26 (see the official releases page ), and the latest patch is 1.37.2. That matters now because the first patches are out. Check whether your managed provider offers 1.37 in your channel yet. The ingress-nginx retirement is also already behind you, so any cluster still relying on it carries unpatched risk into this upgrade.
Short answer: upgrade one minor at a time (1.36 to 1.37, never skipping), and start with 1.37.2 rather than 1.37.0. Before touching anything, scan for deprecated API usage, take an etcd snapshot, and check that your add-ons support 1.37.…