StatefulSet+Headless Service+Selectors

[juancampa]

In #52 we changed the behavior so that it matches the "Without Selector" section here but broke it for services that do have selector.

For services with a selector there should be a DNS entry with the name of the service pointing to all pods that match (i.e. multiple A records), which in our case it transforms to an another entry in /etc/hosts/ of course

[avbhatt]

Hey @juancampa, I'm having this same problem and thinking through some fixes. Using the selectors for a headless service makes sense and would fix the problem, but #52 would be an issue again I believe. Maybe a kubefwd pod does make more sense for something like #52 or an option passed to kubefwd svc to disregard selectors for headless services. It does seem like using selectors when possible should be the default.

[cjimti]

An upgrade to v1.9.0 should resolve this. For headless services kubefwd now forwards the service name to the first Pod if finds, then forwards the backing Pod names individually.