From 22e8d98748cc1bcbd9264656287746044c7c7dc8 Mon Sep 17 00:00:00 2001 From: Maysa Macedo Date: Fri, 2 Mar 2018 07:55:39 +0000 Subject: [PATCH] Add release note for cni health manager This patch contains reno release note for the new feature added regarding cni health manager. Change-Id: I5681b980c40ff29f7cdfe0d7396e652a449d6c2e --- .../cni-health-checks-d2b70f2f2551a9fc.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 releasenotes/notes/cni-health-checks-d2b70f2f2551a9fc.yaml diff --git a/releasenotes/notes/cni-health-checks-d2b70f2f2551a9fc.yaml b/releasenotes/notes/cni-health-checks-d2b70f2f2551a9fc.yaml new file mode 100644 index 000000000..75ee286d0 --- /dev/null +++ b/releasenotes/notes/cni-health-checks-d2b70f2f2551a9fc.yaml @@ -0,0 +1,16 @@ +--- +features: + - | + The CNI daemon now provides health checks allowing the deployer or the + orchestration layer to probe it for readiness and liveness. + + These health checks are served and executed by a Manager that runs + as part of CNI daemon, and offers two endpoints indicating whether + it is ready and alive. + + The Manager validates presence of NET_ADMIN capabilities, health status + of a transactional database, connectivity with Kubernetes API, quantity of + CNI add failures, health of CNI components and amount of memory + being consumed. The health checks fails if any of the presented checks + are not validated, causing the orchestration layer to restart. + More information can be found in the kuryr-kubernetes documentation.