I’m not aware of any security scanner in the environment, but maybe you could advise how to check the source of these connections?
I’ve already tried to add debug annotation(config.linkerd.io/enable-debug-sidecar: "true") to destination deployment, but it didn’t work.
Also, I spotted the same handshake error on linkerd-identity component:
I have managed to deploy debug-sidecar by manually changing deployment manifest(looks like debug annotation didn’t work with core components).
I logged in and ran the following command from debug sidecar:
tcpdump port 8086 -v
This showed me that other sidecars from different services were trying to connect to these internal ports, but they failed.
I guess, the problem is that I accidentally restarted linkerd-identity component, which issued a new certificate and the communication was disrupted with the business services where sidecars had an old one.