Correct, its a hard rule. You can create another pod to house 10.0.x.x hardware to overcome this... Or re-IP the new host to fit in the 172 network. On Aug 11, 2014 5:42 AM, "Hollman Enciso R." <[email protected]> wrote:
> On Sun, Aug 10, 2014 at 8:51 PM, Ahmad Emneina <[email protected]> wrote: > > > I believe your host is expected to be in the same subnet as your pod. In > > this case a172.16.0.x address. > > > > Ahmad thanks for your reply. > > it's not possible to route the traffic and that's it ? > On this case the hosts can reached. > > it is a rule that is so without exception? > > > -- > Hollman Eduardo Enciso R. > http://algolibre.com > @hollman >
