Skip to content
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

Automated backport of #953: Ensure event ordering in the resource syncer #954

Conversation

tpantelis
Copy link
Contributor

Backport of #953 on release-0.18.

#953: Ensure event ordering in the resource syncer

For details on the backport process, see the backport requests page.

If a resource is deleted and then quickly re-created, depending
on timing, the delete event might not get processed so consumers
only observe the re-creation event which is not desirable in some
cases. To ensure events are not missed and are processed in order,
a per-resource queue was added to mantain create and delete operations
in place of the separate created and deleted maps.

Signed-off-by: Tom Pantelis <[email protected]>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr954/tpantelis/automated-backport-of-#953-upstream-release-0.18

@tpantelis tpantelis disabled auto-merge July 19, 2024 12:51
@tpantelis tpantelis merged commit e24eff0 into submariner-io:release-0.18 Jul 19, 2024
16 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr954/tpantelis/automated-backport-of-#953-upstream-release-0.18]

@tpantelis tpantelis deleted the automated-backport-of-#953-upstream-release-0.18 branch February 5, 2025 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants