Comment 2 for bug 1776676

Reviewed: https://review.openstack.org/575119
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=372b835ebb1ebc2592983e3d4cc6dfdc8fa90633
Submitter: Zuul
Branch: master

commit 372b835ebb1ebc2592983e3d4cc6dfdc8fa90633
Author: Antoni Segura Puimedon <email address hidden>
Date: Wed Jun 13 15:45:43 2018 +0200

    process to gracefully exit when last watcher exits

    In case all the watchers (in the CNI case the pod watcher only) have
    gracefully exited, continuing the process only serves to give a false
    appearance of things working. At the same time, it prevents the
    containerized deployment orchestrator from realizing that the Kuryr pod
    is not functional so it does not restart it.

    This fix allows non health proves environments where all watchers have
    gracefully exited to be restarted by k8s/ocp and eventually work again
    should the issue that made the graceful exits happen be solved.

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