-
Notifications
You must be signed in to change notification settings - Fork 1.5k
don't crash on large objets served by recent k8s-api-server #1213
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
Conversation
Per #1209 : now that aws-alb-controller has informers on pods, it's much more likely to be served a object too large for < v1.14 apimachinery serializers. Bump apimachinery dep to 1.14 solves the issue.
Welcome @bpineau! |
Hi @bpineau. Thanks for your PR. I'm waiting for a kubernetes-sigs 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 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bpineau, M00nF1sh 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 |
don't crash on large objets served by recent k8s-api-server
Per #1209 : now that aws-alb-controller has informers on pods, it's
much more likely to be served an object too large for < v1.14
apimachinery serializers.
Bump apimachinery dep to v1.14.0 solves the issue.