Troubleshooting application deployments

Troubleshooting environments and applications typically always looks the same and follows a typical order:

• When was the last deployment?
• What has changed?
• Look at the logs
• Who can access the app and who cannot, if anyone at all?

With Kubernetes, it’s pretty similar when it comes to application troubleshooting. The usual workflow is as follows:

1. Check the app itself running in the container.
2. Check the overall health of the Pod(s).
3. Check the Service or route.

With these three steps, you can usually get to the bottom of what’s happening because, in reality, there can’t be any other problems. It’s either that the app itself isn’t working, the Pod itself has an issue, or the service or route isn’t working as expected.

Although there could only be three potential problems at a high level, when you dive deeper into those problems, there could be various ways...