kube-spawn icon indicating copy to clipboard operation
kube-spawn copied to clipboard

Exposing cluster endpoints and services to the outside

Open schu opened this issue 6 years ago • 0 comments

Currently, kube-spawn doesn't offer a way to expose cluster endpoints and services to the outside world. Endpoints are only reachable from the host kube-spawn is running on and only by

  • setting a route for the service IP range and/or
  • through NodePort type services.

Also, the service IPs overlap, i.e. option 1 (setting a route) doesn't work when running more than a single cluster.

If we want to put kube-spawn in a virtual machine (for example to make it a minikube alternative for macOS users), we need to make sure every cluster gets its own network environment and make that accessible from the outside.

Also, users maybe would like to put kube-spawn cluster behind their loadbalancer; it would be nice if we somehow also allow that.

schu avatar Feb 01 '18 14:02 schu