Currently, we lack support for HStream IO connectors. This causes we can only conduct all connectors by hand (create a configmap first and then create a pod/deployment/statefulset to start sending or receiving data). Assuming we can have a connector object as follows, it will come in handy here (Not the final implementation):

apiVersion: apps.hstream.io/v1alpha2
kind: Connector
metadata:
  name: sink-elastic
spec:
  template:
    auth: basic
    username: elastic
    password: Dzvpsd2d
    # ...
  streams:
    - stream01
    - stream02
  patches:
    stream01:
      offsetStream: connector_offset_for_stream01
    # ...

We will get two elastic search sink connectors that are connected to two different streams. The patches allows users to add extra parameters to different connectors, distinguished by stream.

Future implementations will consider more, and I think an RFC will definitely be needed to describe it.

Any suggestions would be welcome. /cc @s12f @YangKian