Hey folks, question on headless services and endpoint slices I haven’t seen come up.
With a headless service, no selector, and manually managed endpoint slice, is it valid to add a ClusterIP service as an address on that endpoint slice? I understand there are kube-proxy related reasons this sort of endpoint slice would not work with a service with a virtual IP, but if it is a headless service I can’t think of a reason this would not work.
Looking to solve for a service discovery behaviour where we have a workload running distributed between a kube namespace and some remote location(s). We have a proxy for the remote instances in the namespace with ClusterIP services doing port mapping to the proxy, and want an endpointslice with pod ip addresses for the “local” instances and service clusterIPs for the remote instances.
In my limited testing this seems to work, but I haven’t seen this explicitly documented or any prior art.