Generic flow chart to troubleshoot kubernetes deployments
Naninga Karunaratne
![Naninga Karunaratne]()
Naninga Karunaratne
Containerization | Kubernetes Certified CKA/CKAD/KCNA | Azure | AWS | OCI | DevOps | SRE
We know how frustrating troubleshooting deployment/pod failures can get. This is a really good visual flow chart of the generic troubleshooting steps that users can follow. But remember monitoring and logging helps to oversee the issues better.
New Relic Grafana Labs Cloud Native Computing Foundation (CNCF) Microsoft Google Oracle Amazon Web Services (AWS)
Link to the main article click here
Azure Kubernetes Services Technical Advisor at Microsoft
2ythat is an interesting article Naninga. I think it only scratches the surface, but it looks like it would get a person a long ways to fixing things. The flow chart kept my brain busy for a bit while I walked through it in my head :-) I am going to try out the ingress troubleshooting section sometime--curious how it would work to connect to port 80 or 443 on the ingress controller pod directly and still be able to connect to an application knowing that ingress controllers usually get shared among many hostnames, same port.
Newrelic | Solution Consultant | UMass Boston Alumni | Dad
2yThat’s why we have observability!!! To save you all of this time