The old pod log file is not deleted from the /var/log/pods/ directory about kubernetes HOT 14 OPEN

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from kubernetes.

/sig node

from kubernetes.

/sig storage

from kubernetes.

/remove-sig node

from kubernetes.

hi @Black-max12138 , thanks for reporting the issue,
could you verify if the containerLogMaxSize and containerLogMaxFiles settings are correctly configured or not?

from kubernetes.

If these settings are not configured correctly then kubelet may not delete the old log files efficiently because these setting dictate the maximum size each log file can reach before being rotated and the max log files that can be retained !

from kubernetes.

you can also refer to this page for more details !

from kubernetes.

hi @Black-max12138 , thanks for reporting the issue, could you verify if the containerLogMaxSize and containerLogMaxFiles settings are correctly configured or not?

containerLogMaxSize and containerLogMaxFiles are using default values

from kubernetes.

If these settings are not configured correctly then kubelet may not delete the old log files efficiently because these setting dictate the maximum size each log file can reach before being rotated and the max log files that can be retained !

So what is the possibility of this happening if the parameters are set correctly?

from kubernetes.

Generally once the POD is terminated & a new instance is started, the log files associated with the old pod get deleted.

from kubernetes.

AFAIK container logs are managed by sig-node, not by sig-storage
/sig node
/remove-sig node

from kubernetes.

@jsafrane: Those labels are not set on the issue: sig/node

from kubernetes.

hi @Black-max12138 , thanks for reporting the issue, could you verify if the containerLogMaxSize and containerLogMaxFiles settings are correctly configured or not?

By default, Kubernetes truncates the pod’s container log if it reaches 10 MB.
if you want to change the file size, you can set through containerLogMaxSize parameter in the kubelet configuration.
These parameters are not related to delete/persist the log file.

from kubernetes.

/assign @harche

from kubernetes.