You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
At the moment the receiver ingests any object update sent to it during a watch. One of these update types is a DELETE. While occasionally interesting, this type of update is not always needed by a user. For event ingestion, for example, a DELETE option is less useful if the user is only looking for the stream of events that happened in the cluster and is not interested in the cluster's internal management of those events.
Describe the solution you'd like
A new configuration option that allows excluding DELETE types from watches. We could go 1 step further and allow users to specify exactly which operations (ADDED, UPDATED, DELETED, BOOKMARK) the watch should ingest.
Additional context
A feature like this is necessary for #24242 since the k8seventsreceiver does not include DELETE updates.
The text was updated successfully, but these errors were encountered:
…hed objects (#26042)
**Description:**
Adds a new configuration option that allows excluding `DELETED` updates
for watched objects.
**Link to tracking Issue:**
Closes#24904
**Testing:**
New unit tests and tested locally
**Documentation:**
Updated the readme
Component(s)
No response
Is your feature request related to a problem? Please describe.
At the moment the receiver ingests any object update sent to it during a watch. One of these update types is a
DELETE
. While occasionally interesting, this type of update is not always needed by a user. For event ingestion, for example, a DELETE option is less useful if the user is only looking for the stream of events that happened in the cluster and is not interested in the cluster's internal management of those events.Describe the solution you'd like
A new configuration option that allows excluding
DELETE
types from watches. We could go 1 step further and allow users to specify exactly which operations (ADDED
,UPDATED
,DELETED
,BOOKMARK
) the watch should ingest.Additional context
A feature like this is necessary for #24242 since the k8seventsreceiver does not include
DELETE
updates.The text was updated successfully, but these errors were encountered: