Using Sequence with Broker and Trigger

We are going to create the following logical configuration. We create a PingSource, feeding events into the Broker, then we create a Filter that wires those events into a Sequence consisting of 3 steps. Then we take the end of the Sequence and feed newly minted events back into the Broker and create another Trigger which will then display those events.

Prerequisites

  • Knative Serving
  • InMemoryChannel

Note

The examples use the default namespace.

If you want to use different type of Channel, you will have to modify the Sequence.Spec.ChannelTemplate to create the appropriate Channel resources.

Logical Configuration

The functions used in these examples live in https://github.com/knative/eventing/blob/main/cmd/appender/main.go.

Setup

Creating the Broker

  1. To create the cluster default Broker type, copy the following YAML into a file:

    1. apiVersion: eventing.knative.dev/v1
    2. kind: Broker
    3. metadata:
    4. name: default
  2. Apply the YAML file by running the command:

    1. kubectl apply -f <filename>.yaml

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

Create the Knative Services

  1. apiVersion: serving.knative.dev/v1
  2. kind: Service
  3. metadata:
  4. name: first
  5. spec:
  6. template:
  7. spec:
  8. containers:
  9. - image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
  10. env:
  11. - name: MESSAGE
  12. value: " - Handled by 0"
  13. ---
  14. apiVersion: serving.knative.dev/v1
  15. kind: Service
  16. metadata:
  17. name: second
  18. spec:
  19. template:
  20. spec:
  21. containers:
  22. - image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
  23. env:
  24. - name: MESSAGE
  25. value: " - Handled by 1"
  26. ---
  27. apiVersion: serving.knative.dev/v1
  28. kind: Service
  29. metadata:
  30. name: third
  31. spec:
  32. template:
  33. spec:
  34. containers:
  35. - image: gcr.io/knative-releases/knative.dev/eventing/cmd/appender
  36. env:
  37. - name: MESSAGE
  38. value: " - Handled by 2"
  39. - name: TYPE
  40. value: "samples.http.mod3"
  41. ---

Change default in the following command to create the services in the namespace where you have configured your broker:

  1. kubectl -n default create -f ./steps.yaml

Create the Sequence

The sequence.yaml file contains the specifications for creating the Sequence. If you are using a different type of Channel, you need to change the spec.channelTemplate to point to your desired Channel.

Also, change the spec.reply.name to point to your Broker

  1. apiVersion: flows.knative.dev/v1
  2. kind: Sequence
  3. metadata:
  4. name: sequence
  5. spec:
  6. channelTemplate:
  7. apiVersion: messaging.knative.dev/v1
  8. kind: InMemoryChannel
  9. steps:
  10. - ref:
  11. apiVersion: serving.knative.dev/v1
  12. kind: Service
  13. name: first
  14. - ref:
  15. apiVersion: serving.knative.dev/v1
  16. kind: Service
  17. name: second
  18. - ref:
  19. apiVersion: serving.knative.dev/v1
  20. kind: Service
  21. name: third
  22. reply:
  23. ref:
  24. kind: Broker
  25. apiVersion: eventing.knative.dev/v1
  26. name: default

Change default in the following command to create the sequence in the namespace where you have configured your broker:

  1. kubectl -n default create -f ./sequence.yaml

Create the PingSource targeting the Broker

This will create a PingSource which will send a CloudEvent with {“message”: “Hello world!”} as the data payload every 2 minutes.

  1. apiVersion: sources.knative.dev/v1
  2. kind: PingSource
  3. metadata:
  4. name: ping-source
  5. spec:
  6. schedule: "*/2 * * * *"
  7. contentType: "application/json"
  8. data: '{"message": "Hello world!"}'
  9. sink:
  10. ref:
  11. apiVersion: eventing.knative.dev/v1
  12. kind: Broker
  13. name: default

Change default in the following command to create the PingSource in the namespace where you have configured your broker and sequence:

  1. kubectl -n default create -f ./ping-source.yaml

Create the Trigger targeting the Sequence

  1. apiVersion: eventing.knative.dev/v1
  2. kind: Trigger
  3. metadata:
  4. name: sequence-trigger
  5. spec:
  6. broker: default
  7. filter:
  8. attributes:
  9. type: dev.knative.sources.ping
  10. subscriber:
  11. ref:
  12. apiVersion: flows.knative.dev/v1
  13. kind: Sequence
  14. name: sequence

Change default in the following command to create the trigger in the namespace where you have configured your broker and sequence:

  1. kubectl -n default create -f ./trigger.yaml

Create the Service and Trigger displaying the events created by Sequence

  1. apiVersion: serving.knative.dev/v1
  2. kind: Service
  3. metadata:
  4. name: sequence-display
  5. spec:
  6. template:
  7. spec:
  8. containers:
  9. - image: gcr.io/knative-releases/knative.dev/eventing/cmd/event_display
  10. ---
  11. apiVersion: eventing.knative.dev/v1
  12. kind: Trigger
  13. metadata:
  14. name: display-trigger
  15. spec:
  16. broker: default
  17. filter:
  18. attributes:
  19. type: samples.http.mod3
  20. subscriber:
  21. ref:
  22. apiVersion: serving.knative.dev/v1
  23. kind: Service
  24. name: sequence-display
  25. ---

Change default in the following command to create the service and trigger in the namespace where you have configured your broker:

  1. kubectl -n default create -f ./display-trigger.yaml

Inspecting the results

You can now see the final output by inspecting the logs of the sequence-display pods.

  1. kubectl -n default get pods

View the logs for the sequence-display pod:

  1. kubectl -n default logs -l serving.knative.dev/service=sequence-display -c user-container --tail=-1
  2. ☁️ cloudevents.Event
  3. Validation: valid
  4. Context Attributes,
  5. specversion: 1.0
  6. type: samples.http.mod3
  7. source: /apis/v1/namespaces/default/pingsources/ping-source
  8. id: 159bba01-054a-4ae7-b7be-d4e7c5f773d2
  9. time: 2020-03-03T14:56:00.000652027Z
  10. datacontenttype: application/json
  11. Extensions,
  12. knativearrivaltime: 2020-03-03T14:56:00.018390608Z
  13. knativehistory: default-kne-trigger-kn-channel.default.svc.cluster.local; sequence-kn-sequence-0-kn-channel.default.svc.cluster.local; sequence-kn-sequence-1-kn-channel.default.svc.cluster.local; sequence-kn-sequence-2-kn-channel.default.svc.cluster.local; default-kne-trigger-kn-channel.default.svc.cluster.local
  14. traceparent: 00-e893412106ff417a90a5695e53ffd9cc-5829ae45a14ed462-00
  15. Data,
  16. {
  17. "id": 0,
  18. "message": "Hello world! - Handled by 0 - Handled by 1 - Handled by 2"
  19. }

And you can see that the initial PingSource message {"Hello World!"} has been appended to it by each of the steps in the Sequence.