Stateless node keep reaching out to removed storage node

Hey all!
Setup: we use fdb-operator to run foundationdb cluster in kubernetes. We use spec.routing pod. We found the following behavior - after storage node changes ip address
{ “Severity”: “10”, “Time”: “”, “DateTime”: “”, “Type”: “ConnectionClosed”, “ID”: “0000000000000000”, “Error”: “connection_failed”, “ErrorDescription”: “Network connection failed”, “ErrorCode”: “1026”, “SuppressedEventCount”: “1”, “PeerAddr”: “:4501”, “Machine”: “:4501”, “LogGroup”: “foundationdb”, “Roles”: “SS” }
After killing fdbserver in stateless pods (they are bouncing back by fdbmonitor) these logs stop. Is it expected behavior? How we can mitigate this?