Repository navigation
Bump k8s.io/kube-openapi to latest and enable numeric format validation - #136582
Merged
k8s-ci-robot merged 6 commits intoJan 28, 2026
Merged
Conversation
Contributor
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The DetailsInstructions 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. |
Contributor
Author
Member
|
/lgtm |
Contributor
|
LGTM label has been added. DetailsGit tree hash: 803507574748656c2e06d1e5dbdf765109cca546 |
Contributor
Contributor
Author
|
/test pull-kubernetes-e2e-kind |
9 tasks
a7i
added a commit
to a7i/descheduler
that referenced
this pull request
May 19, 2026
Reverts b767b9c. The helper was added to work around what looked like the virt-handler containerdisk-socket race on k8s 1.36, but the actual root cause is unrelated: k8s 1.36's stricter CRD numeric format validation (kubernetes/kubernetes#136582) rejects VMI status updates with the pre-fix uint32 Checksum schema. See kubevirt/kubevirt#17858 for the upstream context and kubevirt/kubevirt#17469 for the upstream fix (merged to main, included in v1.9.0-alpha.0, not in v1.8.x). The follow-up commit bumps KUBEVIRT_VERSION so the test consumes a KubeVirt release that contains the fix, which removes the need for any test-side retry.
a7i
added a commit
to a7i/descheduler
that referenced
this pull request
May 19, 2026
KubeVirt v1.8.2 publishes VMI status checksum fields (uint32 in Go) as format: int32 in its generated CRD schema. k8s 1.36 enables strict numeric format validation in CRDs via kubernetes/kubernetes#136582, which now rejects the legacy schema and causes virt-handler to enter an infinite VMI status update re-enqueue loop. Live migrations never complete and the descheduler e2e TestLiveMigrationInBackground times out. The schema fix landed upstream in kubevirt/kubevirt#17469 (merged to main on 2026-04-18, included in v1.9.0-alpha.0 tagged 2026-05-11) but was not backported to release-1.8, so no v1.8.x release contains it. Bump the default KUBEVIRT_VERSION to v1.9.0-alpha.0 so the e2e suite consumes a release whose generated CRDs are compatible with k8s 1.36's stricter validator. Tracked in kubevirt/kubevirt#17858.
mhan8796
pushed a commit
to mhan8796/kubernetes
that referenced
this pull request
Jun 27, 2026
…pi-format Bump k8s.io/kube-openapi to latest and enable numeric format validation
2 of 5 tasks
1 of 4 tasks
1 of 4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
/kind dependency
What this PR does / why we need it:
This PR bumps k8s.io/kube-openapi to the latest and enables stricter validation for numeric formats in CRDs.
Previously, Kubernetes would strip unrecognized formats for number and integer types during schema processing. This PR updates apiextensions-apiserver to retain valid numeric formats (int32, int64 for integer; float, double for number) so they can be validated by the underlying kube-openapivalidator.
Which issue(s) this PR is related to:
Fixes: #136091
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: