New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add container exit error code between ADD and ContainerDied #95932
Comments
@karan: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig node |
/assign |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/cc |
/remove-lifecycle stale |
@karan I am new to kubelet code, trying to understand. kubernetes/pkg/kubelet/pleg/generic.go Lines 223 to 224 in bce5d7a
other way is to get the exit code from podCache before logging which return pod status. kubernetes/pkg/kubelet/kubelet.go Lines 1958 to 1961 in bce5d7a
|
/assign |
closing this issue, as It has been fixed by #99880 |
@adisky: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What would you like to be added:
Between
and
and
We can't tell if container died with a status error (we can by looking at containerd logs though).
Why is this needed:
It would make debugging dying containers much easier.
The text was updated successfully, but these errors were encountered: