You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2021. It is now read-only.
Kubectl logs has a flag which allows retrieving the logs for an earlier iteration of a pod.
We should also support this and retrieve logs from the previous systemd service that was run for the pod.
Question: would this work across pod boundaries? Not sure when a new invocation id is assigned, what happens when the service crashes and is restarted by systemd, vs the operator deletes the pod and the service is explicitly restarted due to this event?
The text was updated successfully, but these errors were encountered:
Kubectl logs has a flag which allows retrieving the logs for an earlier iteration of a pod.
We should also support this and retrieve logs from the previous systemd service that was run for the pod.
Question: would this work across pod boundaries? Not sure when a new invocation id is assigned, what happens when the service crashes and is restarted by systemd, vs the operator deletes the pod and the service is explicitly restarted due to this event?
The text was updated successfully, but these errors were encountered: