From 065c3db81c292ffca5fd1a96a4466305b6086050 Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Wed, 26 Jul 2023 15:06:23 +0200 Subject: [PATCH] Rewording based on Christophs feedback Signed-off-by: Matthias Wessendorf --- blog/docs/articles/knative-eventing-vision.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/docs/articles/knative-eventing-vision.md b/blog/docs/articles/knative-eventing-vision.md index 54f30ad68a..fefcf0b099 100644 --- a/blog/docs/articles/knative-eventing-vision.md +++ b/blog/docs/articles/knative-eventing-vision.md @@ -73,7 +73,7 @@ The good news is: This breaks the limitation to use the event type metadata with ### CRD for Event Type Definitions -In addition to the above limitation, the fact that for EventType we need established connection between workloads (e.g. PingSource -> Broker) means It is not possible to tell what event type definitions are generally available in Knative Eventing, based on the installed sources/event emitters, independent of running workloads. +The above limitations show that event types are only discoverable when there are running workloads, such as a PingSource sending events to a broker. Without this connection it is not possible to tell what categories of event types are generally available in Knative Eventing installation. To address this problem, Knative Eventing will have a new EventTypeDefinition metadata CRD that captures this information independently of running applications.