Vector daemonSet mounts entire /var/lib directory, causing storage volume unmount issues

[P0lskay]

When deploying the Vector agent as a DaemonSet using the provided Helm chart, the chart mounts the entire host directory /var/lib to the Vector pod. This likely causes Vector to place inotify watches on all contents within /var/lib, including subdirectories like /var/lib/kubelet. As a result, Vector blocks the unmounting of storage volumes mounted under /var/lib/kubelet, preventing clean detachment.

Expected Behavior:

The Vector agent should only mount specific directories required for its operation (e.g., /var/lib/vector or other necessary subdirectories) instead of the entire /var/lib directory. This would prevent Vector from placing inotify watches on unrelated directories like /var/lib/kubelet, avoiding interference with system components.

Actual Behavior:

The Helm chart mounts the entire /var/lib directory, and Vector likely places inotify watches on its contents, including /var/lib/kubelet. This causes Vector to block the unmounting of storage volumes under /var/lib/kubelet.

Proposed Solution:

• Update the Vector Helm chart to:Remove the broad /var/lib hostPath mount.
• Specify and mount only the necessary subdirectories required by Vector (e.g., /var/lib/vector or other specific paths).
• Ensure the chart's default configuration avoids placing inotify watches on critical system directories like /var/lib/kubelet.

[pront]

Hi @P0lskay, I agree that /var/lib/vector/ (and subdirs) is a sensible default for mounting. But we are talking about a breaking change here. As an immediate workaround, you can override this setting with a custom values.yaml or helm CLI.