[META] Auxiliary transports

[finnegancarroll]

Please describe the end goal of this project

This meta issue tracks ongoing work extending the functionality of auxiliary transports in core and plugins.

Auxiliary transports are optional pluggable transports which run on a distinct port/address to the REST API HTTP transport and node-to-node transport. Auxiliary transports support alternative implementations of client/server connections on an OpenSearch cluster.

Possible motivations for a particular auxiliary transport implementation might include exposing a more performant transport protocol or data format on an OpenSearch cluster or more easily integrating OpenSearch into a non-REST environment.

Supporting References

Please find existing auxiliary transport implementations here:

• gRPC alternative to Search/Document APIs
• Arrow/Flight transport server

Issues

• [Core] Add basic client-cert auth TLS settings for auxiliary transports
• [Core] Allow multiple auxiliary transports to be enabled at a time
• [Security Plugin] Add basic client-cert auth TLS settings for auxiliary transports
• [Security Plugin] Make TLS settings distinct for each auxiliary transport
• [Security Plugin] Allow hot swapping of TLS settings for auxiliary transports
• [Security Plugin] Provide basic client certificate authentication of backend users for auxiliary transports.

Related component

Plugins

[andrross]

Catch All Triage - 1