(feat) CloudEvents #298
Merged
(feat) CloudEvents #298
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gianlucam76
force-pushed
the
messging
branch
2 times, most recently
from
7090829 to
073e656
Compare
EventSource can match CloudEvents over NATS/JetStream subjects. EventReports in the managed cluster contains the matching CloudEvents. When EventReport instances are collected, they are processed in the management cluster. If all is successfull, EventReport is stored in the management cluster (with no matching cloudEvents, those are removed before storing it). The EventReport is updated in the managed cluster by removing the processed CloudEvents and setting the status to Processed. If an error happens, EventReport in the managed cluster is not updated. So it will be fetched again and again the matching CloudEvents will be processed. ClusterProfiles/Secrets/ConfigMaps created because of CloudEvents have two labels: 1. eventtrigger.lib.projectsveltos.io/cesource containing the CloudEvent Source 1. eventtrigger.lib.projectsveltos.io/cesubject containing the CloudEvent Subject Resources created because of a CloudEvent are removed only in those scenario: 1. EventTrigger is removed 2. Cluster stops being a match for an EventTrigger 3. EventTrigger.Spec.CloudEventAction is set to ``Delete` The last case is important. It means Sveltos identifies CloudEvents using Source,Subject pair.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EventSource can match CloudEvents over NATS/JetStream subjects.
EventReports in the managed cluster contains the matching CloudEvents. When EventReport instances are collected, they are processed in the management cluster. If all is successfull, EventReport is stored in the management cluster (with no matching cloudEvents, those are removed before storing it). The EventReport is updated in the managed cluster by removing the processed CloudEvents and setting the status to Processed.
If an error happens, EventReport in the managed cluster is not updated. So it will be fetched again and again the matching CloudEvents will be processed.
ClusterProfiles/Secrets/ConfigMaps created because of CloudEvents have two labels:
Resources created because of a CloudEvent are removed only in those scenario:
DeleteThe last case is important. It means Sveltos identifies CloudEvents using Source,Subject pair.