openstack
/
kuryr-kubernetes
Code Issues Proposed changes

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
This commit is contained in:
Maysa Macedo 2018-03-02 07:55:39 +00:00
parent 3ad687f706
commit 22e8d98748
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
releasenotes/notes/cni-health-checks-d2b70f2f2551a9fc.yaml Normal file
View File

@ -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.