Custom volumes and volumeMounts in Vector CR override defaults

[banschikovde]

Description

When custom volumes or volumeMounts are defined in the Vector custom resource (.spec.agent.volumes or .spec.agent.volumeMounts), the operator fully overrides the default set of volumes and mounts used by the Vector Agent DaemonSet.

As a result, all default hostPath mounts such as:

• /var/log
• /var/log/journal
• /var/lib
• /host/proc
• /host/sys

are removed from the resulting PodSpec.

This breaks the default log collection logic — Vector loses access to system and container logs.

Example

apiVersion: observability.kaasops.io/v1alpha1
kind: Vector
metadata:
  name: vector
  namespace: vector
spec:
  agent:
    image: timberio/vector:0.50.0-distroless-libc
    volumes:
      - name: kube-audit
        hostPath:
          path: /var/lib/rancher/rke2/server/logs
          type: DirectoryOrCreate
    volumeMounts:
      - name: kube-audit
        mountPath: /var/log/kubernetes/audit
        readOnly: true

After applying this manifest, the resulting DaemonSet no longer includes the default mounts (e.g. /var/log, /var/lib, /host/sys, /host/proc).

Impact

Vector Agent loses access to container and system log paths,
which causes log collection from pods to stop working.

[aa1ex]

Fixed in #203 (released in v0.3.3).

The merge logic for volumes/volumeMounts has been implemented - custom volumes now properly coexist with defaults instead of causing conflicts.

Note: /var/log and /var/lib are not default mounts for Vector Agent (only for configcheck pod). If you need them, please add them explicitly to your spec - they will now merge correctly with defaults.

Please verify if this resolves your issue.