From 59667f7819a04b255555714826566fa37caad832 Mon Sep 17 00:00:00 2001 From: adamkenihan Date: Wed, 13 Mar 2024 10:44:45 +0000 Subject: [PATCH] Update rfcs/0006-cdevents/README.md Co-authored-by: souleb Signed-off-by: adamkenihan --- rfcs/0006-cdevents/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0006-cdevents/README.md b/rfcs/0006-cdevents/README.md index 35b60ce57e..de4bc43c3b 100644 --- a/rfcs/0006-cdevents/README.md +++ b/rfcs/0006-cdevents/README.md @@ -68,7 +68,7 @@ then this section can be replaced with the actual documentation. Optional if existing discussions and/or issues are linked in the motivation section. --> -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. +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 as part of a Tekton `pipeline`. 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)