-
Notifications
You must be signed in to change notification settings - Fork 846
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
CNI Applications Aren't Allocated ServicePort #4548
Comments
The current Unified Containerizer support in Marathon does not support port mappings. Only host networking is possible at the moment. |
Summary: Port mappings are supported (by Mesos) for more than just Docker, so move PortMapping into Container (as a first step). related to #4548 Test Plan: sbt test Reviewers: nfnt, jasongilanfarr Reviewed By: jasongilanfarr Subscribers: jenkins, marathon-team Differential Revision: https://phabricator.mesosphere.com/D123
@jdef, do we have an ETA when this problem will be solved ? What Marathon ver will the bug fix go under ? Thanks again. |
@jdef, docker containerizer |
bumping the milestone on this. should land in master sooner than later, but won't make the cutoff for marathon 1.4 :( |
Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1687. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8. |
In order to map a marathon task to a service entry in Marathon-LB, it must be allocated a servicePort by Marathon. I have noticed that Marathon is only allocating servicePorts to Docker Containerizer tasks. It is not allocating servicePorts to Unified Containerizer tasks.
As a base case, the the following sample
app.json
launches a docker containerizer task, which is correctly given a servicePort:I see the task's assigned servicePort in its marathon information:
When the above application is launched with the necessary
HAPROXY_*
labels, it works as expected with Marathon-LB.However, the following similar Unified Containerizer task is not assigned a servicePort:
No servicePort is assigned:
When the above application is launched with the necessary
HAPROXY_*
labels, it is not mapped to a service in Marathon-LB (since it does not have a servicePort to assign it to.)cc: @jdef
The text was updated successfully, but these errors were encountered: