Does letting the kubelet write logs that pods emit on their stdout / stderr consume more resources such as CPU and memory, than if the pods wrote their logs directly to a mounted volume? I am asking this considering that the logs are copied from the pod to the kubelet across processes. Or does the disk IO by N pods instead of one kubelet offset any advantage?
I recognize that not letting kubelet handle the logs means kubectl logs ... would not show recent logs. But otherwise, could there be performance advantage to not writing through an intermediary like kubelet?