cni_ds_init unable to distinguish additional containers in kuryr-cni pod

[Michal Dulko]

If there are additional containers in kuryr-cni pod, cni_ds_init is prone to error when choosing on which container `runc exec` or `docker exec` should be executed.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/625900

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/625900
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=65f86ae58e91d272592f1092f247f4bf956e4f77
Submitter: Zuul
Branch: master

commit 65f86ae58e91d272592f1092f247f4bf956e4f77
Author: Michał Dulko <email address hidden>
Date: Tue Dec 18 13:17:05 2018 +0100

    Lookup container name in cni_ds_init

    If your kuryr-cni pod definition consists of multiple containers (e.g.
    you've added an initContainer), cni_ds_init script is prone to error
    when looking up the container running kuryr-daemon. This is becasue it's
    only looking at pod name and namespace. This commit extends it by adding
    container.name=kuryr-cni to the conditions.

    Change-Id: Ib45f6f9f366a62d373c6f37def07e7dcc862726d
    Closes-Bug: 1808969

[OpenStack Infra (hudson-openstack)]

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