---
title: "Discussion on \"CrashLoopBackOff Prod-Anatomy and 10-category Kubernetes Error map\" | Hashnode"
description: "Discussion on \"CrashLoopBackOff Prod-Anatomy and 10-category Kubernetes Error map\". Events are one of my first troubleshooting stops when a Pod isn't behaving as expected. I can inspect them with:\n\nkubectl describe pod <pod-name>\n\nOr kubectl get events -n --sort-by=.lastTimestamp\n\n\nE"
url: "https://hashnode.com/posts/crashloopbackoff-prod-anatomy-and-10-category-kubernetes-error-map/6a98be4c1ee0494720139694"
---

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

Discussion

# [CrashLoopBackOff Prod-Anatomy and 10-category Kubernetes Error map](https://adehorizon.hashnode.dev/crashloopbackoff-prod-anatomy-and-10-category-kubernetes-error-map?utm_source=hashnode&utm_medium=feed)

Events are one of my first troubleshooting stops when a Pod isn't behaving as expected. I can inspect them with: kubectl describe pod <pod-name> Or kubectl get events -n --sort-by=.lastTimestamp E

Sep 3 · 4 min read · adehorizon.hashnode.dev  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#kubernetes-pods](https://hashnode.com/tag/kubernetes-pods)
-   [#cloud](https://hashnode.com/tag/cloud)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#devops](https://hashnode.com/tag/devops)
-   [#kubernetes-architecture](https://hashnode.com/tag/kubernetes-architecture)

## 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.
