Description:

Describe the desired behavior, what scenario it enables and how it
would be used.

Today we only build 1 TLS Socket based on the first Destination Setting associated with the first BackendRef

This needs to be enhanced to support a unique TLS socket per backendref

Should be possible using the tls_socket_matches field https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto