Antoni Segura Puimedon 8f453a2dda cni health: track all cgroup memory usage ... The CNI daemon should always be run in its own cgroup. That typically can take two forms: - Running inside a container - Running as a systemd service This patch changes the way the memory usage is tracked so that both of the cgroup memberships listed above are supported. Thanks to using cgroups for tracking the memory usage, we will finally take into account the CNI daemon children memory usage. Change-Id: I0ef48742653d5c17ea0cc787ae3a997d5d315c5a Closes-Bug: 1752939 Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>		2018-03-06 22:24:58 +01:00
..
binding	Add readiness and liveness checks to CNI.	2018-02-20 14:58:53 +00:00
daemon	Make CNI Registry Plugin namespace aware	2018-03-02 16:09:57 +01:00
plugins	Make CNI Registry Plugin namespace aware	2018-03-02 16:09:57 +01:00
__init__.py	Experimental CNI & VIFBridge binding	2016-12-05 18:05:22 +00:00
api.py	Move cni plugins to a common folder	2018-03-02 16:04:00 +01:00
handlers.py	Delete pods from registry in CNI daemon	2018-02-19 19:21:41 +01:00
health.py	cni health: track all cgroup memory usage	2018-03-06 22:24:58 +01:00
main.py	Move cni plugins to a common folder	2018-03-02 16:04:00 +01:00
utils.py	cni health: track all cgroup memory usage	2018-03-06 22:24:58 +01:00