Skip to content

Developer configuration options

Broker configuration example

The following is a full example of a Channel based Broker object which shows the possible configuration options that you can modify:

kind: Broker
  name: default
  namespace: default
  annotations: MTChannelBasedBroker
    apiVersion: v1
    kind: ConfigMap
    name: config-br-default-channel
    namespace: knative-eventing
        kind: Service
        namespace: example-namespace
        name: example-service
        apiVersion: v1
      uri: example-uri
    retry: 5
    backoffPolicy: exponential
    backoffDelay: "2007-03-01T13:00:00Z/P1Y2M10DT2H30M"
  • You can specify any valid name for your broker. Using default will create a broker named default.
  • The namespace must be an existing namespace in your cluster. Using default will create the broker in the default namespace.
  • You can set the annotation to change the class of the broker. The default broker class is MTChannelBasedBroker, but Knative also supports use of the Kafka and RabbitMQBroker broker class. For more information see the Apache Kafka Broker or RabbitMQ Broker documentation.
  • spec.config is used to specify the default backing channel configuration for Channel based Broker implementations. For more information on configuring the default channel type, see the documentation on Configure Broker defaults.
  • is used to configure event delivery options. Event delivery options specify what happens to an event that fails to be delivered to an event sink. For more information, see the documentation on Event delivery.

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