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
We currently keep dead containers around for several reasons:
To keep container logs and other data around
To keep a record of the container state
It is possible for the container to be GCed before we no longer need this state
We could address these in other ways by:
Storing records for dead containers elsewhere (perhaps the api server?)
Rotating log data to a permanent location (fluentd?)
This would allow us to immediately GC containers once their state and logs had been exported. It would also ensure that we did not lose state or log data due to premature garbage collection.
The text was updated successfully, but these errors were encountered:
Just to mention, the logs stored elsewhere could be safely removed some time actually (those logs of a container corpse within a deleted pod, for example). The logs could take up space after all.
We currently keep dead containers around for several reasons:
We could address these in other ways by:
This would allow us to immediately GC containers once their state and logs had been exported. It would also ensure that we did not lose state or log data due to premature garbage collection.
The text was updated successfully, but these errors were encountered: