'net partition' issue in gossip consensus

[zw0610]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

What happened:

This is an issue I encountered when preparing an example running on a Kubernetes cluster.
The design is use a deployment to start all worker pods and each be will discovered with a service.

However, when the number of replicas is small, it is highly risky that the service will direct the join request to the pot itself, making a pseudo-net-partition situation.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

The IP address of service has nothing to do with the IPs of pods. So far, I can only retry join method for multiple times if returned itself as the only peer.