Pod crash alarms

Last Updated : Apr 22, 2020 |
Prolog information
Metadata
Keywords:

Condition

A KubePodCrash alarm is generated. If pods continuously restart, reports can have incorrect or missing data, or reports fail to run.

Cause

  • Causes for this type of alarm include:
    • Service configuration error
    • Container ran out of memory
    • Application logic error
    • A resource that is expected to be running is currently not available
    • The liveness probe is failing

Solution

  1. If the alarm persists for more than 1 hour, contact Avaya support.