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.
Knative Eventing provides various configuration parameters to control the delivery of events in case of failure. For instance, you can decide to retry sending events that failed to be consumed, and if this didn’t work you can decide to forward those events to a dead letter sink.
Configuring Subscription Delivery
Knative Eventing offers fine-grained control on how events are delivered for each subscription by adding a
delivery section. Consider this example:
apiVersion: messaging.knative.dev/v1 kind: Subscription metadata: name: with-dead-letter-sink spec: channel: apiVersion: messaging.knative.dev/v1 kind: InMemoryChannel name: default delivery: deadLetterSink: ref: apiVersion: serving.knative.dev/v1 kind: Service name: error-handler subscriber: uri: http://doesnotexist.default.svc.cluster.local
deadLetterSink specifies where to send events that failed be consumed by
Common Delivery Parameters
delivery value must be a Delivery Spec
When present, events that failed to be consumed are sent to the
In case of failure, the event is dropped and an error is logged into the system.
deadLetterSink value must be a Destination.
spec: delivery: deadLetterSink: <Destination> retry: <number of retries> backoffPolicy: <linear or exponential> backoffDelay: <ISO8601 duration>
The table below summarizes what delivery parameters are supported for each channel implementation.
|Channel Type||Supported Delivery Parameters|
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.