I have many 3 nodes of MongoDB replica set on Kubernetes, recently we had an incident in our data center that affected our MongoDB clusters, clusters can't do the failover process successfully, to reproduce this issue after the incident I set a NetworkPolicy to block Egress from secondary nodes to the primary node. after applying this Networkpolicy cluster don't have any issues maybe the network policy doesn't drop established connections..., but after I restart one of the MongoDB nodes cluster try to failover and change the primary(unreachable node) with one of the secondary nodes but after a while, it continuously switches primary to secondary and secondary to primary again.