Skip to content

Conversation

@gianlucam76
Copy link
Member

A EventSource starts a watcher on specified resources. Any resource change triggers the EventSource to be reprocessed, which discovers all matching resources and updates the EventReport.

When collectResources is set to false, an EventSource might be processed multiple times even if the list of matching resources hasn't changed. Any EventReport update causes event-manager to reprocess it on the control cluster.

To prevent redundant updates to the EventReport the update can be skipped entirely, provided the matching resources are sorted and maintained in a sorted state within the report.

A EventSource starts a watcher on specified resources. Any resource
change triggers the EventSource to be reprocessed, which discovers
all matching resources and updates the EventReport.

When collectResources is set to false, an EventSource might be processed
multiple times even if the list of matching resources hasn't changed.
Any EventReport update causes event-manager to reprocess it on the control
cluster.

To prevent redundant updates to the EventReport the update
can be skipped entirely, provided the matching resources are sorted
and maintained in a sorted state within the report.
@gianlucam76 gianlucam76 merged commit 5cf8fdd into projectsveltos:main Oct 15, 2025
2 checks passed
@gianlucam76 gianlucam76 deleted the matchingresources branch October 15, 2025 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant