Skip to content


Brokers are Kubernetes custom resources that define an event mesh for collecting a pool of events. Brokers provide a discoverable endpoint for event ingress, and use Triggers for event delivery. Event producers can send events to a broker by POSTing the event.

Source 1 and Source 2 are transmitting some data -- ones and twos -- to the Broker, which then gets filtered by Triggers to the desired Sink.


After an event has entered a broker, it can be forwarded to subscribers by using Triggers. Triggers allow events to be filtered by attributes, so that events with particular attributes can be sent to Subscribers that have registered interest in events with those attributes.


A Subscriber can be any URL or Addressable resource. Subscribers can also reply to an active request from the Broker, and can respond with a new event that is sent back into the Broker.

We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.

× OK