Previous OOM kill detected in container history

critical

availabilityUpdated Feb 24, 2026(via Exa)

Sources

How to Diagnose Envoy Proxy High Memory Usage in Istiooneuptime.com

Technologies:

Envoysubject

Envoy ProxySymptoms of this issue are visible in Envoy Proxy metrics and logs

KubernetesThe root cause of this issue originates in Kubernetes

How to detect:

Container status shows lastState.terminated.reason as OOMKilled, indicating the sidecar has been killed by Kubernetes for exceeding memory limits. Requires either reducing memory usage or increasing limits.

Recommended action:

Review container status and events for OOM history. Investigate root causes using diagnostic commands. Either optimize memory usage through configuration scoping, metric reduction, connection management, or increase memory limits appropriately based on workload needs.