Subscriptions¶

Create a Subscription between a Channel and a Sink by running:

kn subscription create <subscription-name> \
  --channel <Group:Version:Kind>:<channel-name> \
  --sink <sink-prefix>:<sink-name> \
  --sink-reply <sink-prefix>:<sink-name> \
  --sink-dead-letter <sink-prefix>:<sink-name>

• --channel specifies the source for cloud events that should be processed. You must provide the Channel name. If you are not using the default Channel that is backed by the Channel resource, you must prefix the Channel name with the <Group:Version:Kind> for the specified Channel type. For example, this is messaging.knative.dev:v1beta1:KafkaChannel for a Kafka-backed Channel.

• --sink specifies the target destination to which the event should be delivered. By default, the <sink-name> is interpreted as a Knative service of this name, in the same namespace as the Subscription. You can specify the type of the Sink by using one of the following prefixes:

  • ksvc: A Knative service.
  • svc: A Kubernetes Service.
  • channel: A Channel that should be used as the destination. You can only reference default Channel types here.
  • broker: An Eventing Broker.
  • --sink-reply is an optional argument you can use to specify where the Sink reply is sent. It uses the same naming conventions for specifying the Sink as the --sink flag.

  • --sink-dead-letter is an optional argument you can use to specify where to send the CloudEvent in case of a failure. It uses the same naming conventions for specifying the Sink as the --sink flag.

    • ksvc: A Knative service.
    • svc: A Kubernetes Service.
    • channel: A Channel that should be used as destination. Only default Channel types can be referenced here.
    • broker: An Eventing Broker.

  • --sink-reply and --sink-dead-letter are optional arguments. They can be used to specify where the Sink reply is sent, and where to send the CloudEvent in case of a failure, respectively. Both use the same naming conventions for specifying the Sink as the --sink flag.

This example command creates a Subscription named mysubscription that routes events from a Channel named mychannel to a Knative service named myservice.

1. Create a YAML file for the Subscription object using the following example:

   apiVersion: messaging.knative.dev/v1
   kind: Subscription
   metadata:
     name: <subscription-name>
     # Name of the Subscription.
     namespace: default
   spec:
     channel:
       apiVersion: messaging.knative.dev/v1
       kind: Channel
       name: <channel-name>
       # Name of the Channel that the Subscription connects to.
     delivery:
       # Optional delivery configuration settings for events.
       deadLetterSink:
       # When this is configured, events that failed to be consumed are sent to the deadLetterSink.
       # The event is dropped, no re-delivery of the event is attempted, and an error is logged in the system.
       # The deadLetterSink value must be a Destination.
         ref:
           apiVersion: serving.knative.dev/v1
           kind: Service
           name: <service-name>
     reply:
       # Optional configuration settings for the reply event.
       # This is the event Sink that events replied from the subscriber are delivered to.
       ref:
         apiVersion: messaging.knative.dev/v1
         kind: InMemoryChannel
         name: <service-name>
     subscriber:
       # Required configuration settings for the Subscriber. This is the event Sink that events are delivered to from the Channel.
       ref:
         apiVersion: serving.knative.dev/v1
         kind: Service
         name: <service-name>
   

2. Apply the YAML file by running the command:

   kubectl apply -f <filename>.yaml
   

   Where <filename> is the name of the file you created in the previous step.