Comment 6 for bug 1867168

Going through the documentation from MongoDB for running on K8s, AFAICT they do suggest accessing each node directly:
https://docs.mongodb.com/kubernetes-operator/master/tutorial/deploy-replica-set/

I know the client driver has long supported connecting to multiple, as well as discovering new hosts dynamically (connect to one of them, and discover the rest).

So it does seem like a case where they don't want to be hidden behind a service abstraction. It does mean they are sensitive to pods getting rescheduled, but I guess if you use a StatefulSet then their FQDN will be stable.

It seems like we could expose as 'hostname' the FQDN for stateful sets (I'm not sure we want to do it with a normal deployment.)