Skip to content

Kubernetes Troubleshooting

  1. Introduction
  2. ImagePullBackOff
  3. CrashLoopBackOff
  4. Failed to Create Pod Sandbox
  5. Terminated with exit code 1 error
  6. OOM Kills
  7. Pause Container
  8. Preempted Pod
  9. Stuck Namespace
  10. Access PVC Data without the POD
  11. CoreDNS issues
  12. Debugging Techniques and Strategies. Debugging with ephemeral containers
  13. Troubleshooting Tools
    1. Komodor
    2. Palaemon
    3. cdebug and debug-ctr
  14. Slides
  15. Images
  16. Tweets

Introduction

ImagePullBackOff

CrashLoopBackOff

Failed to Create Pod Sandbox

Terminated with exit code 1 error

OOM Kills

Pause Container

Preempted Pod

Stuck Namespace

Access PVC Data without the POD

CoreDNS issues

Debugging Techniques and Strategies. Debugging with ephemeral containers

Troubleshooting Tools

Komodor

Palaemon

cdebug and debug-ctr

  • iximiuz/cdebug a swiss army knife of container debugging. It’s like “docker exec”, but it works even for containers without a shell (scratch, distroless, slim, etc). The “cdebug exec” command allows you to bring your own toolkit and start a shell inside of a running container.
  • felipecruz91/debug-ctr A commandline tool for interactive troubleshooting when a container has crashed or a container image doesn’t include debugging utilities, such as distroless images. Heavily inspired by kubectl debug, but for containers instead of Pods.

Slides

Click to expand!

Images

Click to expand!

learnk8s debug your pods

Tweets

Click to expand!