1. Proposed title of this feature request Support for Multiple interfaces for Docker Container/Pod in Openshift Enterprise 3. What is the nature and description of the request? To create more than one network interface for a docker container or pod on Openshift Enterprise? We have two ethernet interfaces (eth0, eth1) on one host server which are connected to two different networks. The idea is to connect both networks to the docker containers. Does docker daemon or pod currently support connecting multiple network interfaces on a single host? The networking stack can be on flanneld or OpenvSwitch or docker libnetwork. AFAIK, docker libnetwork is not supported for kubernetes. So if there is a solution in flanneld or Openvswitch then it is fine with me. Couple of issues in Docker Libnetwork and Flanneld Github repositories. Both are still open. Added here for your reference: https://github.com/docker/libnetwork/issues/758 https://github.com/coreos/flannel/issues/392 By default every pod has one network interface which can be connected to a network. Our need is to connect more than one interface to the same pod/container. The networking driver can be flanneld or openvswitch. This is for Openshift Enterprise 3.2. Couldn't find any documentation about multiple ethernet interfaces for a pod or container. Not sure if that functionality is already supported or not. This is for Openshift Enterprise 3.2. We have a need to connect more than one network to a single pod or container. Couldn't find any documentation on how to do it for Openshift Enterprise. We are using overlay networks in our setup. For the current Openshift setup we used Openvswitch plugins. We are open to use other networking plugins (ex. flannel) on top of overlay network if it supports our requirement. As already stated, we need to connect two different ethernet interfaces on a server to the same docker container so that the container is connected two different networks. Attached two example configurations using Flannel and Docker libnetwork.
*** This bug has been marked as a duplicate of bug 1346466 ***