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

Convert server API to k8s service and route connected clients properly #85

Closed
timfallmk opened this issue Mar 9, 2018 · 2 comments
Closed

Convert server API to k8s service and route connected clients properly #85

timfallmk opened this issue Mar 9, 2018 · 2 comments
Assignees
@timfallmk
Labels
enhancement

Comments

@timfallmk
Copy link
Contributor

timfallmk commented Mar 9, 2018 •
edited
Loading

Description

Currently synse-server is accessed via the local node address and localhost networking. It should be exposed as a kubernetes service, and thus have a proxied URI. This URI should also be usable by the clients, plugins, prometheus, etc.

Related
@timfallmk timfallmk self-assigned this Mar 9, 2018
@MatthewHink
Copy link
Contributor

Sounds really cool to me. Thanks.

@edaniszewski
Copy link
Contributor

closing - moved issue to appropriate repo for k8s setup

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

@timfallmk timfallmk

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edaniszewski @MatthewHink @timfallmk