A Knative channel is an event-delivery buffer managed by a Broker. It receives events before they are delivered to subscribers, using either simple in-memory storage or persistent storage for greater reliability. section 9.3.3
Choose the channel implementation according to deployment requirements:
- Use an in-memory channel for a simple messaging layer when persistence is not required. section 9.3.3
- Use persistent storage, such as Pub/Sub or Kafka, when reliability requires events to survive processing conditions. section 9.3.3
- Store channel configuration in ConfigMaps and select the configuration through the Broker definition. section 9.3.3
Selecting a default channel
A Broker can reference a ConfigMap that defines the default channel. The Broker then receives events and places messages into its managed channel before sending them to subscribers. section 9.3.3
Use the resource diagram to trace how channels fit between event producers, the Broker, and subscribers in Knative Eventing. section 9.3.3
