Checkpointing for Event loss and deduplication

[akifkhan01]

This component is using k8s.io/client-go/informers to create a watch on K8s-Event object, this informer reads resource ( K8s-Event ) from the source which can cause duplication of data in sink in case of event-exporter going down, to avoid duplication and no loss of Event data, we need checkpointing/bookmark in the application.

Is it handled explicitly by k8s.io/client-go/informers ? Did we think about these failure scenarios, if yes, what was the conclusion ?

@mustafaakin @brianterry

[mustafaakin-atl]

These can be added, but it won't be a simple product then, that we need to have that state with also the leader election. Feel free to work out details if you are willing to contribute. During the original design, we accepted that risk.