---
title: "Diagnosing Pending, CrashLoopBackOff, and OOMKilled"
description: "How can you distinguish Pending, CrashLoopBackOff, and OOMKilled causes?"
status: "coming-soon"
language: "en"
canonical: "https://bulnik.dev/en/articles/topics/T34.09/"
topicId: "T34.09"
---

> Coming soon — this article is being prepared. Below are its question, intended outcome, and place in the story.

## The question

How can you distinguish Pending, CrashLoopBackOff, and OOMKilled causes?

## What we will work through

Distinguish Pending, CrashLoopBackOff, and OOMKilled causes.

## Before you begin

Previously covered: Requests, limits, and QoS; Diagnosing a container that exits immediately.

- [Requests, limits, and QoS](/en/articles/topics/T30.09/)
- [Diagnosing a container that exits immediately](/en/articles/topics/T27.10/)