[
https://issues.apache.org/jira/browse/MESOS-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323626#comment-15323626
]
Qian Zhang commented on MESOS-5578:
-----------------------------------
[~avin...@mesosphere.io], in [CNI spec |
https://github.com/containernetworking/cni/blob/master/SPEC.md#parameters],
there is parameter "CNI_ARGS" which can be used to pass extra argument to the
CNI plugin, and I see the [host-local |
https://github.com/containernetworking/cni/blob/master/Documentation/host-local.md#supported-arguments]
IPAM plugin has already supported "CNI_ARGS" with which user can specify an IP
that he/she wants to assign to the container.
So for any CNI networks which uses host-local IPAM plugin, they will support
static IP address allocation.
> Support static address allocation in CNI
> ----------------------------------------
>
> Key: MESOS-5578
> URL: https://issues.apache.org/jira/browse/MESOS-5578
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Affects Versions: 1.0.0
> Environment: Linux
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
> Labels: mesosphere
>
> Currently a framework can't specify a static IP address for the container
> when using the network/cni isolator.
> The `ipaddress` field in the `NetworkInfo` protobuf was designed for this
> specific purpose but since the CNI spec does not specify a means to allocate
> an IP address to the container the `network/cni` isolator cannot honor this
> field even when it is filled in by the framework.
> Creating this ticket to act as a place holder to track this limitation. As
> and when the CNI spec allows us to specify a static IP address for the
> container, we can resolve this ticket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
