Look at implementing static routes for service and cluster IPs

[viglesiasce]

Currently you are limited to only accessing NodePort services. If kube-solo implemented static routing rules at the OSX layer for both the service IP range and pod IP range this would no longer be the case. As an extension to that you could also implement DNS redirects for cluster.local domains that allowed users to resolve those from the kube-dns pod.

[rimusz]

added @viglesiasce comments from k8s helm channel:

in order to work around that could you implement a static route at the OS level to point the service IPs to the vm ip?
route -n add 10.212.0.0/24 192.168.64.3
where service ip range is 10.212.0.0/24 
could also be done for pod ips

[rimusz]

@AntonioMeireles ^^^

[rimusz]

we are already looking to it. this one is blocked by getting host networking vodooo more resilient (all working when vpn tunnels in use). ideal solution would be to consume docker’s vpnkit - mess is that it isn’t clear that it would be multiVM out of the box (as we are a bit more evolved than them)