IP2service cannot run on the same host as iam4kube

[dadux]

If you run both ip2service and iam4kube on the same host, iam4kube is not working.

When ip2service creates the iptables rules, it creates it for all pods running on the overlay network, and that includes iam4kube. This creates a network loop: When iam4kube tries to reach the (real) AWS metadata service to fetch a role, it ends-up being proxied to itself.

[dadux]

our current workaround is to run iam4kube on a dedicated node.