-
Notifications
You must be signed in to change notification settings - Fork 504
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
Labels
Comments
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. |
@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
given a marathon application with multiple ports, the marathon namer currently supports routing to the first port returned by the marathon api:
linkerd/marathon/src/main/scala/io/buoyant/marathon/v2/Api.scala
Line 80 in fc5ce1e
consider supporting multiple ports, similar to the k8s namer.
The text was updated successfully, but these errors were encountered: