-
Notifications
You must be signed in to change notification settings - Fork 712
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
Pod restarts not showing up in details #2259
Comments
surely the fact that it says 0 is a bug. -> changing labels. |
When pods restart, do their containers get re-created or re-started? |
Good question. I would say they are restarted. I think that the restart count is obtained from docker and I would doubt we have a bug specifically for the kubernetes case. |
Hmmm.
This suggests to me that k8s is counting something different. |
Docker doesn't seem to have a state 'restarted' but rather they have 'restarting' - in the act of restarting. And Kubernetes has a restart policy that determines if the container is restarted or not: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/ |
I think there has been a mix-up here. The details pane shown by @abuehrle (with The restart counts of containers (based on how many times a specific container been restarted) are totally different to those of a container in a pod (based on the number of different dead containers that have not yet been removed). To be even more precise, So, this is really a new feature, which should be fairly easy to implement. |
When I run
kubectl get pods --all-namespaces
in the terminal on the master host in Scope, I see a number of container in the sockshop have restarted:But this information is not displayed on the container and says 0:
The text was updated successfully, but these errors were encountered: