Multiple Cases

    • the first branch accepts events with a time that is is even
    • the second branch accepts events with a time that is is odd

    The events produced by each branch are then sent to the service.

    Please refer to the sample overview for the prerequisites.

    1. kubectl create -f ./filters.yaml -f ./transformers.yaml
    1. apiVersion: serving.knative.dev/v1
    2. kind: Service
    3. metadata:
    4.   name: event-display
    5. spec:
    6.   template:
    7.     spec:
    8.       containers:
    9.         - image: gcr.io/knative-releases/knative.dev/eventing-contrib/cmd/event_display

    Change default below to create the Sequence in the Namespace where you want your resources to be created.

    The parallel.yaml file contains the specifications for creating the Parallel.

    1. apiVersion: flows.knative.dev/v1
    2. kind: Parallel
    3. metadata:
    4.   name: odd-even-parallel
    5. spec:
    6.   channelTemplate:
    7.     apiVersion: messaging.knative.dev/v1
    8.     kind: InMemoryChannel
    9.   branches:
    10.     - filter:
    11.           apiVersion: serving.knative.dev/v1
    12.           kind: Service
    13.           name: even-filter
    14.       subscriber:
    16.           apiVersion: serving.knative.dev/v1
    17.           kind: Service
    18.           name: even-transformer
    19.     - filter:
    20.         ref:
    21.           apiVersion: serving.knative.dev/v1
    22.           kind: Service
    23.           name: odd-filter
    24.       subscriber:
    25.         ref:
    26.           apiVersion: serving.knative.dev/v1
    27.           kind: Service
    28.           name: odd-transformer
    29.   reply:
    30.     ref:
    31.       apiVersion: serving.knative.dev/v1
    32.       kind: Service
    33.       name: event-display
    1. kubectl create -f ./parallel.yaml
    1. kubectl create -f ./ping-source.yaml

    You can now see the final output by inspecting the logs of the event-display pods. Note that since we set the PingSource to emit every minute, it might take some time for the events to show up in the logs.

    Let’s look at the event-display log:

    1. kubectl logs -l serving.knative.dev/service=event-display --tail=30 -c user-container
    3. ☁️  cloudevents.Event
    4. Context Attributes,
    6.   type: dev.knative.sources.ping
    7.   source: /apis/v1/namespaces/default/pingsources/ping-source
    8.   id: 015a4cf4-8a43-44a9-8702-3d4171d27ba5
    9.   time: 2020-03-03T21:24:00.0007254Z
    10.   datacontenttype: application/json; charset=utf-8
    11. Extensions,
    12.   knativehistory: odd-even-parallel-kn-parallel-kn-channel.default.svc.cluster.local; odd-even-parallel-kn-parallel-0-kn-channel.default.svc.cluster.local
    13.   traceparent: 00-41a139bf073f3cfcba7bb7ce7f1488fc-68a891ace985221a-00
    14. Data,
    15.   {
    16.     "message": "we are even!"
    17.   }
    18. ☁️  cloudevents.Event
    19. Validation: valid
    20. Context Attributes,
    21.   specversion: 1.0
    22.   type: dev.knative.sources.ping
    23.   source: /apis/v1/namespaces/default/pingsources/ping-source
    24.   id: 52e6b097-f914-4b5a-8539-165650e85bcd
    25.   time: 2020-03-03T21:23:00.0004662Z
    26.   datacontenttype: application/json; charset=utf-8
    27. Extensions,
    28.   knativehistory: odd-even-parallel-kn-parallel-kn-channel.default.svc.cluster.local; odd-even-parallel-kn-parallel-1-kn-channel.default.svc.cluster.local
    29.   traceparent: 00-58d371410d7daf2033be226860b4ee5d-05d686ee90c3226f-00
    30. Data,
    31.   {
    32.   }