Problem:

Event sources and event sinks are different things. Sources create cloud events and act as an input. Sinks will send a message and act as an output.

In 4.10, we included visualization of Event Sinks in Topology, but that's the only level of support we have in ODC today. There is currently no way to do the following from the OpenShift Dev Console:

• create an event sink
• connect an event source to an event sink
• connect a broker to an event sink
• connect a channel to an event sink

Goal:

Provide an intuitive e2e experience for Kafka Sinks and Kamelet Sinks. This should include:
Creation of Event Sinks: Currently we only have a single event catalog. As we add the ability for Kafka Sinks and kamelet sinks to be created from the UI, we will need to have an additional Event Sink catalog type.

• We should have a separate entrypoint to this catalog from the Add page as well as on the Add to project menu in topology.
• The developer catalog should show Event sinks as well, and include an Event Sink option in the Type faceted filter

Other flows supporting event sinks as valid input

• When creating an event source, an event sink should be a valid input target
• When adding a trigger to a Broker, resources of type Event Sink should be considered "available" subscribers
• When adding a subscription to a Channel, resources of type Event Sink should be considered "available" subscribers
• Note that the 3 flows above should be supported both in forms as well as our drag & drop capabilities

Acceptance criteria:

1. Add an Event Sink Catalog to the Console
   1. Include new tile on Add page which drills into the *Event Sink *catalog
   2. Include new Event Sink Catalog
   3. Include new catalog type in Dev Catalog, thus Event Sinks are shown in Developer catalog along with other items
   4. Provide side panel for Event Sinks, similar to Event Source experience
   5. Provide a form driven experience for Event Sinks by default, as we do for Event Sources
   6. Provide the ability to switch between YAML/Form in the Event Sink creation process
   7. Add to project menu in Topology should have an Event Sink option
2. Broker actions should include an Add Event Sink item after Add Trigger (both in Actions menu & context/right click menu)
3. When dragging the connector of a Broker and dropping on the canvas, an Add Event Sink item should be available after Add Trigger
4. Channel actions should include an Add Event Sink item after Add Subscription (both in Actions menu & context/right click menu)
5. When dragging the connector of a Channel and dropping on the canvas, an Add Event Sink item should be available after _Add Subscription
6. Support visualization of Kafka Sinks ( work needs to be done here to (1) validate that they meet timeframe (2) see what needs to be modified to visualize similarly to 4.10 work for Event Sinks)

Dependencies (External/Internal):

Design Artifacts:

Exploration:

Note: