Problem

Kamelets can be of type source or sink – our initial set were all type sink, but we are now starting to see type SOURCE as well.

Developers don't have the ability to easily discover if kamelets are of type sink or source in the event source catalog nor in the side panel.

Goal

• Provide a filter when the camel-k operator is installed, to allow developers to filter by source/sink.
• Expose that kamelet type (source/sink) in the side panel when selecting an item in the event source catalog.

Why is it important?

Use cases:

1. As a developer, I can distinguish sources and sinks, so that it's easier to find the available options when browing the catalogue

Acceptance criteria:

1. <criteria>

Dependencies (External/Internal):

• Camel K upstream or Camel K by Red Hat (>1.4)

Design Artifacts:

Exploration:

• How do we express support levels (community vs. Red Hat) in a generic way, so that the same expression works in upstreams and downstream contexts?
• Do we need metadata to distinguish KNative capable Kamelets from those ones that might be Kafka specific? The community catalogue might carry both.

Note: