# Kubernetes v1.37: Declarative Validation Drives Record-Breaking API Reviews

DevFeed: [Kubernetes v1.37: Declarative Validation Drives Record-Breaking API Reviews](<https://devfeed.tech/articles/kubernetes-v1-37-declarative-validation-drives-record-breaking-api-reviews-17604.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/08/27/kubernetes-v1-37-declarative-validation/>)

Author: The Kubernetes Authors

Published: 2026-08-27T00:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Code](<https://devfeed.tech/topics/code.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [release](<https://devfeed.tech/tags/release.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [validation](<https://devfeed.tech/tags/validation.md>)

## AI overview

This article reports that Kubernetes v1.37 processed a project-record 118 API review pull requests, up from 88 in v1.36, while reviewers maintained pace. It identifies expanded declarative validation, which reached general availability in v1.36, as a primary efficiency driver; roughly 75% of new validations used declarative validation.

## Source excerpt

Kubernetes v1.37 saw the most API reviews in the project's history. API reviewers reviewed an all-time high of 118 PRs , up from 88 in the v1.36 release. Despite this massive surge, the API reviewers were able to keep pace. A primary driver of this efficiency was the significant expansion of declarative validation (DV), which reached General Availability (GA) in v1.36 and experienced its largest growth to date in v1.37. Declarative validation (DV) allows Kubernetes developers to declare validation rules using Interface Definition Language (IDL) tags (like +k8s:optional or +k8s:minimum=0) directly in the types.go files that define the native API types. These tags are then used by the code generator, validation-gen, to automatically generate the required validation functions, replacing the need for complex, handwritten imperative validation logic. Roughly 75% of new validations were written in DV, significantly saving reviewers' time. Because the tooling handles the complexity, reviewers provided minimal guidance on the validation logic compared to previous releases. Additionally, linters and other correctness checks were a major factor in maintaining this velocity. Pre-reviews conducted by Joel Speed (@joelspeed ), Patrick Ohly (@pohly ), Maciej Szulik (@soltysh ), Tim Allclair (@tallclair ), Joe Betz (@jpbetz ), and Mo Khan (@enj ) saved a lot of time for our core API reviewers like Jordan (@liggitt ) and Tim (@thockin ). (A special congratulations to Joe, who was promoted to API approver this release!) "The guardrail work that made use of declarative validation tags automatically require covering test cases made a big difference in 1.37. Validation expressed as declarative tags shrank the complexity of implementations and reviews, and is feeding a virtuous cycle where reviewers and authors prefer declarative validation once they get used to it. There were a few PRs this cycle that had almost no validation.go changes at all (🎉), and a lot where all the straightforwa