-
Notifications
You must be signed in to change notification settings - Fork 50
Update k8s.io/kube-openapi digest to 865597e #1583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
red-hat-konflux
wants to merge
1
commit into
main
Choose a base branch
from
konflux/mintmaker/main/k8s.io-kube-openapi-digest
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+3
−3
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/lightspeed-operator
Length of output: 371
🌐 Web query:
k8s.io/kube-openapi commit 865597e52e25 changelog security💡 Result:
I couldn’t locate any source that ties the specific kube-openapi commit 865597e52e25 to a changelog entry or a security fix. What I did find: a recent kube-openapi update in Kubernetes that mentions “key changes upstream” (including an escaping bugfix for JSON-Pointer-reserved characters in generated schema/component names) in PR
#138741, but that PR’s referenced kube-openapi revision is b7f5293f4787—not 865597e52e25—and the snippets available don’t mention security implications. Security-related material I found for kube-openapi is general (e.g., the repo’s SECURITY.md and an OpenAPI V3 security requirements PR), but it’s not associated with commit 865597e52e25. So, based on the evidence available from the searches, I can’t confidently answer what security/changelog item 865597e52e25 corresponds to. If you can share the full 40-char commit hash (or a link to the commit/compare view), I can try again and specifically map it to the relevant kube-openapi changelog/security note(s).Citations:
🌐 Web query:
k8s.io/kube-openapi compatibility with kubernetes 0.35.4💡 Result:
For Kubernetes v0.35.4, compatibility is achieved by using the kube-openapi version that Kubernetes itself vendors/depends on for that release. In the v0.35.4 line, the kube-apiserver (and related components) depend on k8s.io/kube-openapi at v0.0.0-20250910181357-589584f1c912 [1][2]. In other words: kube-openapi is not “version-compatible” across arbitrary Kubernetes versions; you should align kube-openapi to the Kubernetes release’s expected module version (above) to avoid OpenAPI generation/aggregation mismatches. What this means in practice 1) If you are building extension API servers or clients: match kube-openapi to the Kubernetes branch/release you’re targeting (for k8s 0.35.4, use the kube-openapi commit/version listed above) [1][2]. 2) If you mix versions (kube-openapi newer/older than what kube-apiserver expects), you can hit OpenAPI backward-incompatibility issues—e.g., kube-openapi changes around how model names are generated for OpenAPI v2 aggregation can be backward-incompatible and require Kubernetes-side bumps / kube-openapi bumps [3][4]. Source-backed anchor for Kubernetes OpenAPI generation The kube-apiserver’s OpenAPI handler imports kube-openapi packages (k8s.io/kube-openapi/pkg/util and pkg/validation/spec), so kube-apiserver and kube-openapi must be kept in lockstep for that Kubernetes release series [2].
Citations:
Fix k8s.io/kube-openapi alignment with Kubernetes v0.35.4 (go.mod line 167)
865597e52e25exists inkubernetes/kube-openapi(dated 2026-06-03).k8s.io/kube-openapireturns no reported advisories for the queried package.k8s.io/kube-openapi v0.0.0-20250910181357-589584f1c912, but this PR pinsv0.0.0-20260603220949-865597e52e25while keepingk8s.io/api,k8s.io/apimachinery, andk8s.io/client-goatv0.35.4. Align kube-openapi to the v0.35.4 expected module version (or bump the full Kubernetes dependency set together) to avoid OpenAPI aggregation/generation mismatches.🤖 Prompt for AI Agents