这是indexloc提供的服务,不要输入任何密码
Skip to content

APIServerSource filter event type sent to sink #7791

@rh-hemartin

Description

@rh-hemartin

Problem
Currently APIServerSource sends create, update and delete event types to the sink specified. Our use case can benefit of receiving just delete events instead. This will reduce the load our receiver experiences. Instead of discarding the message on the receiver we will discard it on the producer (the APIServerSource).

The APIServerSource resource could support an additional optional property called spec.eventTypes that is a list that allows for create, update and delete as values. By default the three of them would be specified, so the current behaviour is retained.

This introduces a if/else for each message so performance is reduced for the default case (current behavior), however there are performance gains when some events are excluded. The most important performance gain would be if the user removes the update event type. I'm trying to come up with a solution that does not reduce performance for the default case.

Persona:
Which persona is this feature for? Event Consumer and Event Producer

Exit Criteria
The event types sent to the sink are of the type selected.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions