DOCS - config.linkerd.io/skip-outbound-ports Port Ranges

[jseiser]

Is this documentation correct? https://linkerd.io/2-edge/reference/proxy-configuration/

config.linkerd.io/skip-outbound-ports - Outbound ports that should skip the proxy. Comma-separated list of values, where each value can be a port number or a range a-b. - Outbound ports that should skip the proxy. Comma-separated list of values, where each value can be a port number or a range a-b.

We are hitting a 10 second timeout, that We are thinking is a protocol detection issue, but these ports should already be marked opaque.

linkerd check --proxy is returning this

‼ opaque ports are properly annotated
        * failed to convert 24000-24009 to port number for pod telemetry-qa4-dev-5b75b85c6c-9r5np
        * failed to convert 24000-24009 to port number for pod telemetry-qa6-dev-544c7cd89b-5m9fd
        * failed to convert 24000-24009 to port number for pod telemetry-qa1-dev-67d87b6c47-54zwn
        * failed to convert 24000-24009 to port number for pod telemetry-qa5-dev-84d967b6fb-fmhdw
        * failed to convert 24000-24009 to port number for pod telemetry-qa6-dev-544c7cd89b-5m9fd
        * failed to convert 24000-24009 to port number for pod telemetry-qa3-dev-6dc466f675-s4f4b
        * failed to convert 24000-24009 to port number for pod telemetry-qa4-dev-5b75b85c6c-9r5np
        * failed to convert 24000-24009 to port number for pod telemetry-qa1-dev-67d87b6c47-54zwn
        * failed to convert 24000-24009 to port number for pod telemetry-qa2-dev-6d5d7d4f9d-tldzs
        * failed to convert 24000-24009 to port number for pod telemetry-qa5-dev-84d967b6fb-fmhdw

But both the Pod, and the service, already have those ports as being marked opaque

kind: Pod
metadata:
  annotations:
    config.linkerd.io/opaque-ports: 25,587,3306,4444,5432,6379,9300,11211,8000,24000-24009,4222,7422

kind: Service
metadata:
  annotations:
    config.linkerd.io/opaque-ports: 25,587,3306,4444,5432,6379,9300,11211,8000,24000-24009,4222,7422

So im not sure if the linkerd check --proxy is just an invalid check, and doesnt understand the port range, or if the documentation is wrong, and port-range is actually not being set and the ports are not marked opaque