-
Notifications
You must be signed in to change notification settings - Fork 533
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
slo-monitor: the pulling image time of the pod is incorrectly recorded as 1970-01-01 00:00:00 +0000 UTC #2525
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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-sigs/prow repository. |
What happened:
The slo-monitor collects pod lifecycle time by watching events, but it incorrectly records the time of starting pulling image.
I0122 02:27:28.157857 1 pod_monitor.go:324] Observed Pod default/netshoot creation: created 2024-01-22 02:27:21 +0000 UTC, pulling: 1970-01-01 00:00:00 +0000 UTC, pulled: 2024-01-22 02:27:26 +0000 UTC, running: 2024-01-22 02:27:28.157849816 +0000 UTC m=+1186.391220756
What you expected to happen:
The time of pulling image is recorded correctly.
How to reproduce it (as minimally and precisely as possible):
Deploy the slo-monitor in k8s cluster with --v=5, create a common pod.
And then observe the log like above.
The text was updated successfully, but these errors were encountered: