The Kubernetes objects raise alerts and alert symptom for instances that are available in the cluster.
| Alert Definition | Symptoms | Severity | Recommendation |
|---|---|---|---|
| Container CPU limit is set to unlimited | Container CPU limit is not defined | Info | A container running without CPU limit may claim all of Node's resources. Modify your Pod configuration with a CPU limit on the affected container. A quick glimpse at the CPU usage trend can help you set the limit. |
| Container CPU usage is high | Container CPU usage is higher than 90% Container CPU usage is higher than 80% Container CPU usage is higher than 70% |
Critical Immediate Warning |
Consider the option of increasing CPU limit on the affected container if Node's resources permit. Else, you may have to add a new Node to the cluster to ease out the CPU crunch. |
| Container Memory limit is set to unlimited | Container Memory limit is not defined | Info | A container running without Memory limit may claim all of Node's resources. Modify your Pod configuration with a Memory limit on the affected container. A quick glimpse at the Memory usage trend can help you set the limit. |
| Container is not available | Container is not available | Immediate |
Redeploy the Pod and make sure it goes to Ready state |
| Container Memory usage is high | Container Process CPU usage is higher than 90% Container Process CPU usage is higher than 80% Container Process CPU usage is higher than 70% |
Critical Immediate Warning |
Consider the option of increasing Memory limit on the affected container if Node's resources permit. Else, you may have to add a new Node to the cluster to ease out the Memory crunch. |
| Container Process has high Memory Usage | Container Process Memory usage is higher than 90% Container Process Memory usage is higher than 80% Container Process Memory usage is higher than 70% |
Critical Immediate Warning |
Consider increasing CPU limit of the container. |
| Container Process has high Memory Usage | Node Process Memory usage is higher than 90% Node Process Memory usage is higher than 80% Node Process Memory usage is higher than 70% |
Critical Immediate Warning |
Consider increasing Memory limit of the container. |
| Master Node is not available | Master Node is not available | Immediate | Ensure that the Master Node is reachable and API server is up and running. |
| Namespace is not Available | Namespace is not Available | Immediate | Check if the namespace has been deleted |
| Node has high CPU Usage | Node CPU usage is higher than 90% Node CPU Memory usage is higher than 80% Node CPU Memory usage is higher than 70% Node CPU Memory usage is higher than 60% |
Critical Immediate Warning Info |
Consider increasing CPU resource of the Node OR add a new Node to the cluster |
| Node is not available | Node is not available | Immediate | Verify if the Node is reachable and in Ready state |
| Node has high Memory Usage | Node Memory usage is higher than 90% NodeMemory usage is higher than 80% NodeMemory usage is higher than 70% NodeMemory usage is higher than 60% |
Critical Immediate Warning Info |
Consider increasing Memory resource of the Node OR add a new new Node to the cluster |
| One of the Pods has highest CPU usage on Namespace | Pod with highest utilization on namespace has CPU usage higher than 90% Pod with highest utilization on namespace has CPU usage higher than 80% Pod with highest utilization on namespace has CPU usage higher than 70% Descendant pod object (OR Operation) Pod memory usage is higher than 70% Pod memory usage is higher than 80% Pod memory usage is higher than 90% |
Critical Immediate Warning Info |
Consider modifying the affected Pod configurations to increase CPU limits |
| One of the pods has high Memory usage on Namespace | Pod with highest utilization on namespace has memory usage higher than 90% Pod with highest utilization on namespace has memory usage higher than 80% Pod with highest utilization on namespace has memory usage higher than 70% Descendant pod object (OR Operation) Pod CPU Usage is higher than 70%Pod CPU Usage is higher than 80% Pod CPU Usage is higher than 90% |
Critical Immediate Warning Info |
Consider modifying the affected Pod configurations to increase Memory limits |
| One of the pods has high CPU usage on Service | Pod with highest utilization on Service has CPU usage higher than 70% Pod with highest utilization on Service has CPU usage higher than 80% Pod with highest utilization on Service has CPU usage higher than 90% Descendant pod object (OR Operation) Pod CPU Usage is higher than 70% Pod CPU Usage is higher than 80% Pod CPU Usage is higher than 90% |
Critical Immediate Warning |
Consider modifying the affected Pod configurations to increase CPU limits |
| One of the pods has high Memory usage on Service | Pod with highest utilization on Service has memory usage higher than 70% Pod with highest utilization on Service has memory usage higher than 80% Pod with highest utilization on Service has memory usage higher than 90% Descendant pod object (OR Operation) Pod memory usage is higher than 70% Pod memory usage is higher than 80% Pod memory usage is higher than 90% |
Critical Immediate Warning |
Consider modifying the affected Pod configurations to increase Memory limits |
| Pod has high CPU Usage | Pod CPU Usage is higher than 90% Pod CPU Usage is higher than 80% Pod CPU Usage is higher than 70% Pod CPU Usage is higher than 60% |
Critical Immediate Warning Info |
Go through the individual usage of the affected Pod's containers and balance their CPU limits. |
| Pod has high Memory Usage | Pod memory usage is higher than 90% Pod memory usage is higher than 80% Pod memory usage is higher than 70% Pod memory usage is higher than 60% |
Critical Immediate Warning Info |
Go through the individual usage of the affected Pod's containers and balance their Memory limits. |
| Pod is not available | Pod is not available | Critical | Redeploy the Pod and make sure it goes to Ready state |
| ReplicaSet is not available | ReplicaSet is not available | Immediate | Make sure that the Replica Set is present. |
| Service is not available | Service is not available | Immediate | Make sure that the Service is present. |
| Sum of Resource Requests of Pods exceed Node Capacity | CPU Requests greater than node capacity Memory Requests greater than node capacity |
Critical | Minimum CPU/Memory resources required to run the Pods of the affected node has exceeded Node capacity. Consider increasing Node resources OR add more Nodes to distribute the workload. |
