Troubleshooting in Kubernetes

POD with replica set count is two
  • Events
  • Restart time of the POD
  • Traffic during POD restart
  • Reason for POD restart
  • Termination grace period
  • Readiness and Liveness Prob
kubectl get events -n namespace pod_name
kubectl describe pod -n namespace pod_name | grep 'Start Time'
kubectl describe pod -n namespace pod_name
Exit Code 0: Absence of an attached foreground process
Exit Code 1: Indicates failure due to application error
Exit Code 137: Indicates failure as container received SIGKILL
Exit Code 139: Indicates failure as container received SIGSEGV
Exit Code 143: Indicates failure as container received SIGTERM

--

--

--

DevOps Engineer with 10+ years of experience in the IT Industry. In-depth experience in building highly complex, scalable, secure and distributed systems.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Fix the “Sorry, This File Type Is Not Permitted for Security Reasons” Error in WordPress

The future of cloud computing

Threads in Java — Part 1

The Costs of Developing an Mobile App

Crisp Guideline on How to Start Coding as a Beginner?

API Design: Designing for errors, actually matters!

Viper Cache Review: Bonus+Demo

Viper Cache Review: Bonus+Demo

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ankur

Ankur

DevOps Engineer with 10+ years of experience in the IT Industry. In-depth experience in building highly complex, scalable, secure and distributed systems.

More from Medium

Introduction to Openshift Operators

Structural container patterns in Kubernetes

KEDA: Kubernetes Based Event-driven Autoscaling with SpringBoot and RabbitMQ

Debugging namespace deletion issue in Kubernetes