AMQP Adaptor for AMQP workloads #2343
Description
Is your feature request related to a problem? Please describe.
There is no clean way for AMQP based services to access the Skupper data plane natively. Since the data plane is an AMQP network, it would be beneficial for AMQP-enabled workloads to be able to access the network directly in order to offer and use services.
Describe the solution you'd like
The equivalent of a Listener/Connector for AMQP would be needed. This could be a new type in the current Listener and Connector CRDs or new CRDs could be introduced for this feature.
One of the problems with using the current CRDs is that AMQP has different semantics from TCP:
- AMQP does not have a client/server role pairing for connections. It is a symmetric protocol.
- A routing-key is not required for AMQP endpoints since the keys would be specified at run time by the workloads.
- There is no notion of matching listeners/connectors in AMQP.
Both listener and connector must be provided to allow for flexibility in how AMQP connections are established.
It is required that AMQP endpoints (both listener and connector) include an optional list of permitted routing keys for receive and send that restrain access by the connected workloads.