[InPlacePodVerticalScaling] ResizePolicy field is not being validated

[gjkim42]

What happened?

#102884 (comment)

The newly added field ResizePolicy field is not being validated.

@vinaykul @liggitt

What did you expect to happen?

ResizePolicy field should be validated.

How can we reproduce it (as minimally and precisely as possible)?

We can create a pod with invalid ResizePolicy to reproduce this.

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[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.

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/test-infra repository.

[liggitt]

/assign @vinaykul
/sig node
/priority important-soon
/milestone v1.27
adding to 1.27 milestone to resolve if possible

[gjkim42]

I'll try this for v1.27 if you don't mind.

[liggitt]

getting a PR open, reviewed, and green is always good. we'll evaluate it for risk and if there's a second release candidate we can likely include it

[vinaykul]

Nice catch! Please review fix: #116857

This likely got dropped either during port-over of the original PR or during bad rebase. I should not have left the resize policy e2e tests for beta.

Gotta run to get my kid prepped, dr. appt and then school drop. So I'll try and add an E2E test for this later today. please hold for e2e test (but we should fix this in 1.27)

[vinaykul]

@gjkim42 I realized you were working on a fix as well only after I sent my fix out and was catching up on emails at doc office (rushed morning). I didn't mean to step over your effort to fix it, sorry about that.

[gjkim42]

I am completely fine with that. Thanks for the fix :)