-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Manual cherry pick of kube-openapi changes for release-1.21 #106255
Manual cherry pick of kube-openapi changes for release-1.21 #106255
Conversation
Hi @ulucinar. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/assign @apelisse @DangerOnTheRanger |
commented at kubernetes/kube-openapi@65ecc9d#r746087650, but I would not expect to bump dependencies like this on release branches. |
same likely applies for 1.20, but I didn't check that yet |
f28aedc
to
69e345d
Compare
69e345d
to
759b69b
Compare
759b69b
to
64ce4b7
Compare
Bump kube-openapi against kube-openapi/release-1.21 branch Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
64ce4b7
to
57b8a2b
Compare
Both of the |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, ulucinar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks a lot @ulucinar ! |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Updates
kube-openapi
dependency to consume the aggregated OpenAPI spec lazy-marshaling behavior introduced with:kubernetes/kube-openapi#251
and cherry picked to the
kube-openapi/release-1.21
branch with:kubernetes/kube-openapi#265
Looks like lazy-marshaling introduced with kubernetes/kube-openapi#251 enables us to better scale in the #-of-CRDs-per-cluster dimension.
Which issue(s) this PR fixes:
Fixes #101755
Fixes #105932
Does this PR introduce a user-facing change?
/cc @apelisse
/cc @DangerOnTheRanger
/sig api-machinery