Update API/KIND version

[shunki-fujita]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

The version specified in the Makefile is out of date and needs to be updated.

kustomize/kyaml/openapi/Makefile

Lines 8 to 9 in bb7a280

	KIND_VERSION := "v0.11.1"
	API_VERSION ?= "v1.21.2"

Why is this needed?

Can't get information on recently added APIs like ValidatingAdmissionPolicy.
https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/

Can you accomplish the motivating task without this feature, and if so, how?

It is possible by manually updating the version and building

What other solutions have you considered?

Have no other ideas.

Anything else we should know?

No response

Feature ownership

• I am interested in contributing this feature myself! 🎉

[shunki-fujita]

Hello, @koba1t

I'm currently working on updating the API_VERSION. The policy written below is outdated, so I'm unsure which version should be specified instead.
https://github.com/kubernetes-sigs/kustomize/tree/master/kyaml/openapi#choose-the-new-version-to-use

Do you have any thoughts on this matter?

[chansuke]

@shunki-fujita
Thank you so much for your work!

This is just my personal opinion.
I'd like to choose v1.30.4 according to the documentation.

The reason is below:

• v1.30.4 maintains compatibility with older versions while also ensuring access to new features.
• v1.31.0 introduces breaking changes, and compared to that, v1.30.4 appears to be more stable.

And the direction you taking is good IMHO.

[shunki-fujita]

@chansuke
I'll proceed with that approach. Thank you!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[koba1t]

refer: #5016

I agree to support new Kubernetes APIs.
But if we update the openapi version,a few users got effect due to new openapi is removed some beta API definition.
Therefore, It seems difficult to accept the content of simply update openapi.

/area openapi
/triage accepted
/kind feature