[davidgamero]

summary

• replace the old minor-per-kubernetes wording with concise semver guidance and a link to New Release Needed. #2582
• correct generation targets for 0.19–0.22 and add 2.0.0–2.0.2; list released versions only
• separate generated api targets from cluster compatibility, retaining the transport migration notes

background

the original minor-per-kubernetes policy appears in #548 and the 1.x migration plan.

in august 2025, brendan proposed:

Major version increments aligned with k8s version increment.

source

colin agreed:

I'm good with following semver, and I agree that aligning K8s releases with majors simplifies things.

source

application has been inconsistent: 1.4.0 retained the old numbering, and #2845 initially proposed a subsequent kubernetes update as 2.1.0. the current release split is illustrated by #3087 (1.37 regeneration), #3131 (3.0.0 preparation on main), and #3130 (2.0.2 on release-2.0).

this draft synthesizes those discussions for maintainer confirmation; the readme keeps the user-facing guidance brief.

table verification

checked src/gen/swagger.json at each listed tag. 0.19.0–0.22.0 target kubernetes 1.27–1.30, one version earlier than the previous chart. the 2.0.x settings still name 1.35, but the shipped schema and 2.0.0 release notes identify 1.36.

validation

• git diff --check
• push hooks passed: 423 source tests, lint, build-with-tests, and 423 transpiled tests

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davidgamero

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [davidgamero]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[brendandburns]

Maybe add 3.0.0 or HEAD for 1.37?