Alexander Rukletsov commented on MESOS-8534:

[~sagar8192] Will this affect http and tcp health checks? Currently we assume 
that the default executor is always in the same network namespace as its tasks. 
We can relax this to "the default executor can always reach its tasks / send a 
TCP message", but anything more will require code changes in the checker 

> Allow nested containers in TaskGroups to have separate network namespaces
> -------------------------------------------------------------------------
>                 Key: MESOS-8534
>                 URL: https://issues.apache.org/jira/browse/MESOS-8534
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Sagar Sadashiv Patwardhan
>            Priority: Minor
>              Labels: cni
> As per the discussion with [~jieyu] and [~avinash.mesos] , I am going to 
> allow nested containers in TaskGroups to have separate namespaces. I am also 
> going to retain the existing functionality, where nested containers can 
> connect to parent/root containers namespace.

This message was sent by Atlassian JIRA

Reply via email to