Hello there. I'm currently using EKS v1.11.5 (control plane only) and just noticed that one of my pod failed a week ago. Kubernetes automatically created a new pod right away, so there was no downtime, but still want to debug what really happened. I tried to get logs from the failed pod but it only returned me container ``` "" in pod "" is not available ``` Is there any way to track down this problem deeply? Like kubernetes audit-logging from control plane? Thanks. + Maybe something left on syslog of worker nodes, but I blocked ssh connection to nodes for security reasons. so it's not possible for now.

How to debug pod failure on EKS?

Hello there.

I'm currently using EKS v1.11.5 (control plane only) and just noticed that one of my pod failed a week ago.

Kubernetes automatically created a new pod right away, so there was no downtime, but still want to debug what really happened.

I tried to get logs from the failed pod but it only returned me container

"<deployment-name>" in pod "<pod-name>" is not available

Is there any way to track down this problem deeply? Like kubernetes audit-logging from control plane?

Thanks.

Maybe something left on syslog of worker nodes, but I blocked ssh connection to nodes for security reasons. so it's not possible for now.

주제

태그

언어

English

질문됨 6년 전609회 조회

1개 답변

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

As long as you have not removed the pod you could do

kubectl describe pod ....

It should indicate why the pod failed, could be due to OOM or other resource failure etc.

답변함 6년 전