Kubernetes now seems to destroy the veths before running Teardown, so it's no longer possible to find the OVS port a container was attached to, so we have to use different logic to clean up after them.
(Last time I stupidly tested against the kube plugin so didn't notice I hadn't fully fixed the multitenant plugin...)
Kubernetes now seems to destroy the veths before running Teardown, so it's no longer possible to find the OVS port a container was attached to, so we have to use different logic to clean up after them.
(Last time I stupidly tested against the kube plugin so didn't notice I hadn't fully fixed the multitenant plugin...)
@pravisankar