Dead container walking: making a case for Kubernetes Object Status
octant release David EspejoAs a Kubernetes practitioner, you may be familiar with kubectl and how to interpret the results you get from a very common command like:
# kubectl get pods # NAME READY STATUS RESTARTS AGE 3scale-kourier-control-54cc54cc58-px2dt 1/1 Running 3 4d2h activator-67656dcbbb-hq62r 0/1 Running 161 4d2h autoscaler-df6856b64-blxgm 1/1 Running 1 4d2h But in case you are not, it could be challenging to accurately diagnose the behavior shown in the above example: the activator Pod is in a Running status but none of its containers are Ready.
Read more...