Problem
Event producers want to know at publish time when an event is useful and when it can be dropped. This allows for greater efficiency for use cases in which the majority of events are uninteresting.
Persona:
Producer or Operator (operator's concern is maintaining network QoS)
Exit Criteria
An event source inside the namespace is able to determine in advance of publishing an event whether a consumer has registered interest in that event. The event can be dropped without making a network request (intra-pod network requests are allowed).
Propagation delay of the advertisement is allowed.
Time Estimate (optional):
Additional context (optional)
Open question whether event sources outside the namespace or outside the cluster should be able to detect this advertisement.
(Optional) Metrics may be developed to measure propagation delay of the advertisement, and an SLO may been defined. Propagation delay may be detectable by publishers.
Problem
Event producers want to know at publish time when an event is useful and when it can be dropped. This allows for greater efficiency for use cases in which the majority of events are uninteresting.
Persona:
Producer or Operator (operator's concern is maintaining network QoS)
Exit Criteria
An event source inside the namespace is able to determine in advance of publishing an event whether a consumer has registered interest in that event. The event can be dropped without making a network request (intra-pod network requests are allowed).
Propagation delay of the advertisement is allowed.
Time Estimate (optional):
Additional context (optional)
Open question whether event sources outside the namespace or outside the cluster should be able to detect this advertisement.
(Optional) Metrics may be developed to measure propagation delay of the advertisement, and an SLO may been defined. Propagation delay may be detectable by publishers.