Configure strategies to auto-wire declarative validation

[jpbetz]

What type of PR is this?

/kind api-change

What this PR does / why we need it:

• Strategies can now opt-in to declarative validation, eliminating the need to write special code in Validation and ValidationUpdate functions to enable DV.
• Add a cross-cutting test to verify that all strategies in the kubernetes codebase opt-in to declarative validation.
• Migrate all strategies so that the cross-cutting test passes.

Other notes:

• This does not enable code generation for all APIs. DV will effectively be a no-op for APIs without validation codegen.
• This is part of a larger set of changes to make it impossible to have DV tags in types.go files that are ignored by validation

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

No. This change is a no-op from a user perspective.

NONE

[k8s-ci-robot]

Please note that we're already in Code Freeze for the upcoming v1.36.0 release.

Adding the milestone to this PR is strictly prohibited without proper approval. If this PR needs to be included in the v1.36.0 release:

1. Technical review: get the PR reviewed and approved as usual (/lgtm and /approve)
2. Inclusion in release: ping @sig-release-leads on the #sig-release Slack channel and suggest to add the v1.36.0 milestone to the PR

---

We're also in Test Freeze for the release-1.36 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.36.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Fri Apr 10 20:19:08 UTC 2026.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jpbetz
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• pkg/api/testing/OWNERS [jpbetz]
• pkg/controlplane/OWNERS [jpbetz]
• pkg/registry/OWNERS
• staging/src/k8s.io/apiserver/OWNERS [jpbetz]

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

[jpbetz]

/assign @lalitc375

cc @thockin @aaron-prindle @yongruilin

/sig api-machinery

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[k8s-ci-robot]

@jpbetz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-kind	c7e3fb8	link	true	/test pull-kubernetes-e2e-kind
pull-kubernetes-e2e-gce	c7e3fb8	link	true	/test pull-kubernetes-e2e-gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.