Difference between container port,host port and service port in dcos json in portMappings

Question

I am confused with what all these port signify container port,host port and service port in portMappings, below is my json

"portMappings": [
  {
    "containerPort": 9000,
    "hostPort": 9000,
    "labels": {
      "VIP_0": "/app2n:9000"
    },
    "protocol": "tcp",
    "servicePort": 10101
  }
]

score 16 · Accepted Answer · answered Jan 09 '18 at 09:41

16

containerPort is the port in the container, one which your containerized app should listen on,
hostPort is the port which will be visible on the Mesos Agent where container is running,
servicePort is abstract port for internal use of framework, e.g. it can be used in loadbalancer as port mapped to host on which your run your container and its hostPort. Should be unique across your cluster.

Basically flow looks like this: internet -> <loadbalancer e.g. nginx, haproxy>:<servicePort> -> <mesos agent on which container runs>:<hostPort> -> <container>:<containerPort>

answered Jan 09 '18 at 09:41

Mateusz Moneta

1,500
1
10
7

3

the heck is a `targetPort` then? – Randy L Oct 12 '18 at 15:15
@the0ther TargetPort is the port on the actual pod that requests are sent to. – Alexej Magura Oct 10 '19 at 17:32

score 0 · Answer 2 · answered Feb 14 '19 at 13:58

0

A targetPort This is the port on the pod that the request gets sent to. Your application needs to be listening for network requests on this port for the service to work. These ports are typically used in service yaml descriptors.

answered Feb 14 '19 at 13:58

Rory Savage

63
8

Difference between container port,host port and service port in dcos json in portMappings

2 Answers2