-
Notifications
You must be signed in to change notification settings - Fork 40.7k
dynamic client: remove support for API streaming #132229
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
dynamic client: remove support for API streaming #132229
Conversation
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 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-sigs/prow repository. |
/assign @wojtek-t |
73137f4
to
cb8d644
Compare
ginkgo.By("Verifying if the secret list was properly streamed") | ||
streamedSecrets := secretList.Items | ||
gomega.Expect(cmp.Equal(expectedSecrets, streamedSecrets)).To(gomega.BeTrueBecause("data received via watchlist must match the added data")) | ||
secretInformer := cache.NewSharedIndexInformer( |
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.
smart
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.
This also proves that streaming works for a dynamic informer. But I was planning to add a dedicated test for a dynamic informer anyway.
Vendoring failure seems related - other than that LGTM |
8ad3d97
to
1d69a2f
Compare
fixed. |
/lgtm |
LGTM label has been added. Git tree hash: eb2c71fe2fab077a68c653fe9815ccb50ed9a115
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial, wojtek-t 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR is related to:
Special notes for your reviewer: xref: #125305
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: