This message was deleted.
# logging
a
This message was deleted.
p
This is only relevant for the logs managaed by kubelets for use by kubectl and such. If you build an ELK stack, then the data will be saved there as well and not rotated.
l
if the logs cannot be processed by the log collector (fluentbit) soon enough, then the logs are getting lost indeed
a
What can we do to mitigate the same... and are logs of evicted pods removed from file system
@powerful-librarian-10572 is there a possibility that the logs of an evicted pod are deleted before the fluent bit collector runs. I agree that once fluentbit collects and sends to ELK it is safe
p
I mean 0 risk doesnt exist lmao.
However, pod eviction should only occur on node event, therefore those logs might not be of high importance anyway. If you are scared about pod logs on crash not being collected, this shouldnt occur.
l
eviction can happen also if the scheduler needs resources for a higher priority pod, but if you have workloads where logs are critical, then use guaranteed QoS or priorityclasses, etc
p
Yeah thats what i mean by node event, a pod wont get evicted by its own request 😄
l
right
p
Granted i shouldnt be tarking too much about log collection reliabilty as i STIL CANT SETUP EFFIN LOKI
l
loki is not easy to operate
🫠 1