Filebeat: daemonset mounting /var/lib/kubelet/pods not seeing new pvc data

We have a filebeat daemonset in our kubernetes cluster and we have mount the /var/lib/kubelet/pods hostpath from the host node so we can collect log data stored on pvc's. When a new application pod comes online and a new pvc is attached to that pod, the pvc directory is visible in /var/lib/kubelet/pods on the filebeat daemonset pod on the applicable node, however, the data on that pvc is not visible. If we delete that pod and allow a new one to spin up in its place, the data is now visible.

Any easier way to make this data visible to the filebeat pod?

1 Like

Bump

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.