OCPBUGS-59756: Fix IntOrString cost estimation when schema has a MaxLength constraint

[JoelSpeed]

This PR fixes an issue where the estimated CEL runtime cost of IntOrString types in Kubernetes are miscalculated, due to the ignorance of the openapi schema max length property for the string

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-59756, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR fixes an issue where the estimated CEL runtime cost of IntOrString types in Kubernetes are miscalculated, due to the ignorance of the openapi schema max length property for the string

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@JoelSpeed: the contents of this pull request could be automatically validated.

The following commits are valid:

• 56a0b6c|UPSTREAM: 132837: Fix IntOrString cost estimation when schema has a MaxLength constraint: the upstream PR kubernetes/kubernetes#132837 has merged
• b9708bc|UPSTREAM: 132837: Add test case to prove MaxElements correctly set on IntOrString: the upstream PR kubernetes/kubernetes#132837 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[JoelSpeed]

/jira refresh

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-59756, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@JoelSpeed: 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
ci/prow/e2e-metal-ipi-ovn-dualstack	b9708bc	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-ovn-ipv6	b9708bc	link	false	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-disruptive	b9708bc	link	false	/test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-hypershift	b9708bc	link	true	/test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-techpreview-serial	b9708bc	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/configmap-scale	b9708bc	link	true	/test configmap-scale
ci/prow/e2e-gcp-ovn-upgrade	b9708bc	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/verify	b9708bc	link	true	/test verify
ci/prow/e2e-openstack-csi-cinder	b9708bc	link	false	/test e2e-openstack-csi-cinder
ci/prow/unit	b9708bc	link	true	/test unit
ci/prow/e2e-aws-ovn-crun	b9708bc	link	true	/test e2e-aws-ovn-crun

Full PR test history. Your PR dashboard.

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.