Description of problem:

Sink-type KameletBinding cannot be created directly from the dev console, but users can create them manually via YAML.

They are KameletBinding resources where the source is a Knative channel/broker and the sink is a Kamelet with label camel.apache.org/kamelet.type=sink.

E.g.

kind: KameletBinding
...
spec:
  source:
    ref:
      kind: Channel
      name: telegram-channel
  sink:
    ref:
      kind: Kamelet
      name: telegram-sink 

When such an object is created, a Knative Service will be created and a trigger/subscription bound to it. The KameletBinding object will be parent of both service and trigger/subscription.

Ideally this should be displayed as a source, with arrow going from the channel/broker to the service, but visualization is split as in the attached image (bottom-left). Service is displayed correctly, but the telegram icon stands apart.

Visualization may also look incorrect (not tested) also with KameletBindings that are unrelated to Knative (e.g. we can use KafkaTopic from kafka.strimzi.io as source or sink).

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Install Camel K operator, any version
2. Create a knative channel
3. Create a source from telegram using the console, but before saving it, take the yaml, swap source and sink, replace telegram-source with telegram-sink, add a property "chatId" set to 1 (or a valid Telegram chat Id)
4. Look at the ODC console

Actual results:

Displayed in the image.

Expected results:

Arrow from channel to service with Telegram icon. Telegram icon not detached.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

-

Additional info:

-