Antoni Segura Puimedon f4769c3516 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 Depends-On: https://review.openstack.org/583922 Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com> (cherry picked from commit 372b835ebb)		2018-07-19 12:47:42 +02:00
..
binding	Fix kubelet retries issues	2018-01-04 19:20:06 +01:00
daemon	process to gracefully exit when last watcher exits	2018-07-19 12:47:42 +02:00
__init__.py	Experimental CNI & VIFBridge binding	2016-12-05 18:05:22 +00:00
api.py	CNI split - introducing CNI daemon	2017-11-21 08:50:04 +01:00
handlers.py	Delete pods from registry in CNI daemon	2018-02-22 18:12:08 +01:00
main.py	CNI split - introducing CNI daemon	2017-11-21 08:50:04 +01:00
utils.py	CNI split - introducing CNI daemon	2017-11-21 08:50:04 +01:00