devstack host can't probe pods

[Antoni Segura Puimedon]

Commit 79a00b27b892eee0765bafc860fa9aa73ea40c3b introduced separate nets for pod and services. Up until that moment, we had been using the private network for pods, hence, the interface we put in the host namespace in the private interface was enough to probe the pods.

There's two solutions that I can see:

a) Add routes to the separate networks
b) Make the host interface in the pod subnet

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/487935
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=9ca51776522c1148166bdf53eedddc7dc06ee294
Submitter: Jenkins
Branch: master

commit 9ca51776522c1148166bdf53eedddc7dc06ee294
Author: Antoni Segura Puimedon <email address hidden>
Date: Thu Jul 27 18:23:27 2017 +0200

    devstack: create host interface to the pod subnet

    Patch set If5a49bc2010ea59965c5ee9570fb5d131cdf4089 meant that the host
    ovs interface was no longer in the pod subnet, meaning that the probes
    would return "no route to host".

    This patch addresses it by correcting the network selection.

    Change-Id: Ic6cacd3e2271f23b7141e0f1fce0d5f1a718ba6e
    Closes-Bug: #1707009
    Signed-off-by: Antoni Segura Puimedon <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 0.2.0 release.