Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make spawner work from arbitrary machine #22

Closed
andrewgdotcom opened this issue Jun 11, 2018 · 1 comment
Closed

Make spawner work from arbitrary machine #22

andrewgdotcom opened this issue Jun 11, 2018 · 1 comment
Assignees
@andrewgdotcom

Comments

@andrewgdotcom
Copy link
Contributor

Currently the spawner assumes that it is running on the es-controller, and bakes it into the http_proxy and firewall configurations.

http_proxy should always go via the es-controller - but we don't want to hard code its IP. Perhaps we could discover it?

The firewall allows the originating machine by default - but that won't work in general if the cluster has no routable IPs and/or if the spawner is run from behind NAT. This is a more general problem though - if there is no connectivity then there is no way to interact with the cluster at all after creation. VPN routing is one possible solution.
@andrewgdotcom andrewgdotcom self-assigned this Jun 11, 2018
@andrewgdotcom andrewgdotcom mentioned this issue Jun 12, 2018
Closed
andrewgdotcom added a commit that referenced this issue Aug 13, 2018
@andrewgdotcom
Allow override of CONTROLLER_IP for #22
b922e74
@andrewgdotcom
Copy link
Contributor Author

Port forwarding is being handled in #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewgdotcom andrewgdotcom

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andrewgdotcom