Hi there !
We test monitoring our kubernetes cluster via zabbix with the "Kubernetes nodes by HTTP" template version 6.2.1
When a container is failing in a pod, kubernetes tries to restart it until it reaches the "CrashLoopBackoff" state. But while a container inside a pod is in this state, no alert is shown in zabbix.
When any container is in "CrashLoopBackoff" state, a warning should be triggered by default.
Steps to reproduce:
1. Create a faulty container, let's call it Gorbatchev
2. wait until it reaches the CrashLoopBackoff state
No alert is shown.
A "trigger prototype" should be added to the template to alert when any pod has Conditions: Containers ready to false.
We were going to create the trigger on our zabbix instance but maybe this should be the default on the template ? Any pod in this state is an issue for cluster admins to investigate IMO.
Thanks in advance