This message was deleted.
# generala
adamant-kite-43734
09/28/2023, 8:30 AMThis message was deleted.
s
shy-tent-66642
09/29/2023, 2:25 PMJust bumping this
c
creamy-pencil-82913
09/29/2023, 4:08 PMOne of the containers using that image is writing logs into the image filesystem. These are changes are ephemeral, and will be discarded when the pod goes away, but still consume space. You should mount a tempfs volume for the application logs and/or implement log rotation at the application level.
creamy-pencil-82913
09/29/2023, 4:08 PMKubernetes doesn’t solve the problem of application logging for you. If it creates a bunch of files on disk, that is still something you need to address.
s
shy-tent-66642
09/29/2023, 4:13 PMThanks I will check with our Devs. In the meantime, even if I delete the pod (assume deployment has 3 pods min) one by one & it creates a new pod the logs will still consume space. Right?
So I am thinking i will just echo "" > access.log as a dirty fix.
c
creamy-pencil-82913
09/29/2023, 4:27 PMno, the files should go away when you delete the pods. any changes made to the overlayfs are discarded when the container terminates.
creamy-pencil-82913
09/29/2023, 4:28 PMyou might look at setting
readOnlyRootFilesystem: true👀 1
s
shy-tent-66642
09/29/2023, 4:33 PMOk...so if log files go away upon pod deletion, that would free up space I guess