Skip to content
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.

Exposing cluster endpoints and services to the outside #264

Open
schu opened this issue Feb 1, 2018 · 0 comments
Open

Exposing cluster endpoints and services to the outside #264

schu opened this issue Feb 1, 2018 · 0 comments

Comments

@schu
Copy link
Contributor

schu commented Feb 1, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant