Default port no longer considered opaque in 2.13.0 #10745
Description
What is the issue?
After upgrading to 2.13.0, we are seeing protocol detection warnings to a service that uses port 25:
INFO ThreadId(03) outbound:proxy{addr=10.132.1.212:25}: linkerd_detect: Continuing after timeout: linkerd_proxy_http::version::Version protocol detection timed out after 10s
I have tried setting the opaque annotation on the destination service to work around this but it made no difference:
annotations:
config.linkerd.io/opaque-ports: "25"
I raised an unrelated issue on the forum about a behaviour change with default opaque ports here, and it seems this may be also a consequence of whatever behavioural change caused that error.
How can it be reproduced?
I would assume spin up any service using port 25.
Logs, error output, etc
INFO ThreadId(03) outbound:proxy{addr=10.132.1.212:25}: linkerd_detect: Continuing after timeout: linkerd_proxy_http::version::Version protocol detection timed out after 10s
output of linkerd check -o short
Status check results are √
Environment
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.16-gke.1400", GitCommit:"822bbca3cfca1ac13d8c759cc72496ffd10b5f59", GitTreeState:"clean", BuildDate:"2023-02-07T09:39:01Z", GoVersion:"go1.19.5 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}
Linkerd 2.13.0
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
None