Skip to content

Explicitly suppor handling missed events for Informers #1727

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.

Sign up for GitHub

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

Jump to bottom
Closed
csviri opened this issue Jan 20, 2023 · 1 comment
Closed

Explicitly suppor handling missed events for Informers #1727

csviri opened this issue Jan 20, 2023 · 1 comment
Assignees
@csviri
Milestone
4.3

Comments

@csviri
Copy link
Collaborator

csviri commented Jan 20, 2023 •
edited
Loading

It is possible to miss some events with an informer, it's not the case that we don't receive any event, it can happen that some events are missed, while a watch is restarted in an informer (and a re-list needs to be done, thus cannot continue from a resourceVersion).

To have a workaround and don't miss events, a periodic list might be possible to mitigate this.

see use case:
https://kubernetes.slack.com/archives/C0EG7JC6T/p1673376066590699

But this is quite a corner case.
@csviri csviri changed the title Explicitly supporting missed events for Informers Explicitly suppor handling missed events for Informers Jan 20, 2023
@csviri csviri added this to the 4.3 milestone Jan 20, 2023
@csviri csviri self-assigned this Jan 24, 2023
@csviri
Copy link
Collaborator Author

csviri commented Jan 24, 2023

Closing this until not requested from us explicitly.

@csviri csviri closed this as completed Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csviri csviri

Labels
None yet
Projects
None yet
Milestone
4.3
Development

No branches or pull requests
1 participant
@csviri