Are these WARN logs critical?

[ultratin]

Hi, I'm investigating some warn logs from a linkerd-injected service in my cluster:

  70 WARN ThreadId(01) dst:controller{addr=linkerd-dst-headless.linkerd.svc.cluster.local:8086}:endpoint{addr=10.26.27.61:8086}: linkerd_reconnect: Failed to connect error=endpoint 10.26.27.61:8086: Connection refused (os error 111) error.sources=[Connection refused (os error 111)]
   9 WARN ThreadId(01) dst:controller{addr=localhost:8086}:endpoint{addr=127.0.0.1:8086}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8086: Connection refused (os error 111) error.sources=[Connection refused (os error 111)]
 100 WARN ThreadId(01) policy:controller{addr=linkerd-policy.linkerd.svc.cluster.local:8090}:endpoint{addr=10.26.27.61:8090}: linkerd_reconnect: Failed to connect error=endpoint 10.26.27.61:8090: Connection refused (os error 111) error.sources=[Connection refused (os error 111)]
  12 WARN ThreadId(01) policy:controller{addr=localhost:8090}:endpoint{addr=127.0.0.1:8090}: linkerd_reconnect: Failed to connect error=endpoint 127.0.0.1:8090: Connection refused (os error 111) error.sources=[Connection refused (os error 111)]

The proxy couldn't connect to the destination (8086) and policy (8090) controllers. I also see some localhost connection failures which I'm not sure about.
After investigating, I found the linkerd-destination pod was evicted by Karpenter (node consolidation) around the same time these errors occurred. The pod was cleanly terminated, no OOMKill or crash.
A couple of questions:

Are these warnings expected during control plane pod eviction/rescheduling, or do they indicate a real issue?
What are the localhost:8086 / localhost:8090 connection attempts? Is that the proxy trying to reach something local?
Does transient control plane unavailability cause failed requests, or does the data plane continue working?

Thanks!