---
title: "Discussion on \"Solving ImagePullBackOff, CrashLoopBackOff and OOMKilled  Pod-Status in K8s\" | Hashnode"
description: "Discussion on \"Solving ImagePullBackOff, CrashLoopBackOff and OOMKilled  Pod-Status in K8s\". The real Kubernetes troubleshooting skill isn't memorizing error names, it's knowing which layer to check next based on the symptom in front of you.\nkubectl describe pod <pod-name> + Events is one of"
url: "https://hashnode.com/posts/solving-imagepullbackoff-crashloopbackoff-and-oomkilled-pod-status-in-k8s/6a98adef9a580ce10044adc1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Solving ImagePullBackOff, CrashLoopBackOff and OOMKilled Pod-Status in K8s](https://adehorizon.hashnode.dev/solving-imagepullbackoff-crashloopbackoff-and-oomkilled-pod-status-in-k8s?utm_source=hashnode&utm_medium=feed)

The real Kubernetes troubleshooting skill isn't memorizing error names, it's knowing which layer to check next based on the symptom in front of you. kubectl describe pod <pod-name> + Events is one of

Sep 2 · 5 min read · adehorizon.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#aws](https://hashnode.com/tag/aws)
-   [#eks](https://hashnode.com/tag/eks)
-   [#devops](https://hashnode.com/tag/devops)
-   [#oomkilled](https://hashnode.com/tag/oomkilled)
-   [#pod](https://hashnode.com/tag/pod)
-   [#crashloopbackoff](https://hashnode.com/tag/crashloopbackoff)
-   [#k8s](https://hashnode.com/tag/k8s)

## Written by

[Adedoyin Ogunsola](https://hashnode.com/@adegram)

@adegram

  
[View profile](https://hashnode.com/@adegram)

AWS Cloud Engineer | DevOps | 2x AWS Certified | Terraform | Kubernetes

## Responses

Markdown supported · ⌘↵ to post

No responses yet.