Skip to content

Commit

Permalink
Update rfcs/0006-cdevents/README.md
Browse files Browse the repository at this point in the history
Co-authored-by: souleb <[email protected]>
Signed-off-by: adamkenihan <[email protected]>
  • Loading branch information
adamkenihan and souleb authored Mar 13, 2024
1 parent 55fddfc commit 67a51b8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion rfcs/0006-cdevents/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Optional if existing discussions and/or issues are linked in the motivation sect
-->

Users of multiple different CI/CD tools such as Tekton and Flux could use CDEvents as a potential way to enable interoperability. For example, a user may want a Flux resource to reconcile after Tekton has done something.
Using Tekton the user triggers something that will fire off a CDEvent to the CloudEvents Broker. A subscription that the user will have set up externally [with the broker](https://knative.dev/docs/eventing/brokers/) will then send a relevant CDEvent to the CDEvent Receiver within Flux based on the configuration.
The Tekton `pipeline` will fire off a CDEvent to the CloudEvents Broker. A subscription that the user will have set up externally, e.g. with the [knative broker](https://knative.dev/docs/eventing/brokers/) will then send a relevant CDEvent to the CDEvent Receiver within Flux.

![usecase](cdevents-flux-tekton.png)

Expand Down

0 comments on commit 67a51b8

Please sign in to comment.