-
Notifications
You must be signed in to change notification settings - Fork 128
[release-4.21] OCPBUGS-73910: UPSTREAM: 135340: cbor: bump limits #2565
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
base: release-4.21
Are you sure you want to change the base?
Conversation
with the current established limits we can see the following error: ``` failed to list <object>: unable to determine group/version/kind: cbor: exceeded max number of elements 1024 for CBOR array. ```
|
@benluddy: This pull request references Jira Issue OCPBUGS-73910, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
@benluddy: the contents of this pull request could be automatically validated. The following commits are valid:
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by me |
|
@benluddy: This PR has been marked as verified by DetailsIn response to this:
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. |
|
@benluddy: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/label backport-risk-assessed |
We have the client gate disabled in 4.21 because it's not practical to backport this to all clients, but the server-side impact is limited to kube-apiserver only (custom resource storage decoding).