Handle HTTP protocol traffic over opaque transport connections #6178
Description
Based on the issue identified in #6160 when config.linkerd.io/opaque-ports is set on a workload but not on the corresponding service, we still do protocol detection even though the traffic is proxied over an opaque transport connection.
Traffic is sent to the proxy's inbound port, however, the connection fails once it reads the opaque transport header:
[ 19.551490s] DEBUG ThreadId(01) inbound:accept{client.addr=10.42.0.100:39078}:server{port=4143}:direct: linkerd_transport_header::server: Read transport header header=TransportHeader { port: 8080, name: None, protocol: Some(Http2) }
[ 19.551569s] INFO ThreadId(01) inbound:accept{client.addr=10.42.0.100:39078}: linkerd_app_core::serve: Connection closed error=a named target must be provided on gateway connections
We could handle HTTP traffic in such cases more gracefully.