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.

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

marathon namer: support multiple ports #1253

Open
siggy opened this issue Apr 27, 2017 · 2 comments
Open

marathon namer: support multiple ports #1253

siggy opened this issue Apr 27, 2017 · 2 comments

Comments

@siggy
Copy link
Member

siggy commented Apr 27, 2017

given a marathon application with multiple ports, the marathon namer currently supports routing to the first port returned by the marathon api:

addr.flatMap(_.discovery).flatMap(_.ports).flatMap(_.headOption).flatMap(_.number)

consider supporting multiple ports, similar to the k8s namer.

@olix0r
Copy link
Member

olix0r commented May 3, 2017

The port name could either be encoded in the name itself (as is done in kubernetes) or this could be made an explicit configuration option on the namer.

@IssueHuntBot
Copy link

@BoostIO funded this issue with $10. Visit this issue on Issuehunt

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

No branches or pull requests

3 participants