-
Notifications
You must be signed in to change notification settings - Fork 276
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
Prevent panic when informer receives cache.DeletedFinalStateUnknown #7776
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
oh, missed the spelling linter lol |
ae2ec82
to
bd45d38
Compare
ok, that looks better ;) /lgtm |
/retest |
Is it reasonable to add a unit test for these cases in |
I don't see a way to do this easily. The function that's changed is within the |
@JoelSpeed: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Makes sure that the
cache.DeletedFinalStateUnknown
event is handled correctly, when an informer for endpoint slices becomes temporarily disconnected and misses an event.Updates the logic to correctly type assert and avoid panicking if the event is not as expected.
Which issue(s) this PR fixes:
Fixes #7775
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: