Kubernetes 1.36 Notes

Kubernetes 1.36 shipped on April 22 with release notes that read more like a literary essay than a changelog. (kubernetes.io) Kubernetes is the open-source system many companies use to run containers, the packaged units that hold an application and its dependencies across clusters of servers. Version 1.36, named “Haru,” closed a 15-week cycle that ran from January 12 to April 22 and drew contributions from 491 people at 106 companies. (kubernetes.io 1) (kubernetes.io 2) The official release post says 1.36 includes 70 enhancements, with 18 moving to Stable, 25 entering Beta, and 25 entering Alpha. The release team tied the theme to Japanese words for spring, clear skies, and distance, and said the logo was inspired by Hokusai’s *Thirty-six Views of Mount Fuji*. (kubernetes.io) Release notes are the upgrade manual operators read before they touch production systems, because Kubernetes changes can break traffic, storage, or application behavior if teams miss a deprecation. The project’s own migration docs route users to changelogs, searchable release notes, and a deprecated-application programming interface guide before upgrades. (kubernetes.io 1) (kubernetes.io 2) That focus on upgrade reading has gotten sharper as Kubernetes has kept its three-releases-a-year cadence and about one year of patch support for each branch. The project says 1.36 is now the latest active branch, alongside 1.35 and 1.34. (kubernetes.dev) (kubernetes.io 1) (kubernetes.io 2) The 1.36 cycle also landed during a broader cleanup of aging infrastructure around Kubernetes networking. Kubernetes said in November 2025 that Ingress NGINX would retire in March 2026, and in January warned there would be no more bug-fix or security releases after retirement. (kubernetes.io) (kubernetes.io) By late February, the project was publishing migration advice that compared Ingress NGINX behavior with Gateway API, the newer way to define how outside traffic reaches services in a cluster. That guidance stressed that even a “correct” translation could still cause outages if teams missed old controller quirks. (kubernetes.io) The release team’s wording stood out enough that The Register wrote about the notes themselves, not just the software. Its report said the prose and artwork turned a routine infrastructure release into an example of how maintainers can package operational guidance for readers who still have to do the upgrade work. (theregister.com) The practical next step is less poetic: operators still have to read the deprecations, check the migration guides, and test 1.36 before rollout. Kubernetes just gave them a release note they may be more likely to finish. (kubernetes.io) (kubernetes.io)