Zero: error logs about broken pipe

Hey,

I have deployed a simple Dgraph cluster via helm chart v24.0.5 on a three node self hosted Kubernetes cluster.

On a totally new installation every zero pod logs every 10 seconds an error message like this:

E1223 12:11:23.512475       1 x.go:352] Could not send error msg=write tcp 10.111.54.190:6080->89.XXX.XXX.115:49574: write: broken pipe code=ErrorNoData due to http error write tcp 10.111.54.190:6080->89.XXX.XXX.115:49574: write: broken pipe

Has anybody an idea what does this mean? (probably any liveness probe)
I am wondering about the message content, because the “->” implies to me that the connection goes from the private IP of the zero pod (outgoing on port 6080) to the public IP (incoming on a random port) of the host the zero pod is running. Well this should be the other way around, right?

Could this be caused because I don’t use any ingress (disabled in the values for the helm chart)?

Thanks for any hint to get rid of it.