1. Proposed Title of this Feature Request

Allow Customization of --collector.filesystem.mount-points-exclude Argument in OpenShift Node Exporter

2. What is the Nature and Description of the Request?

The current implementation of the node-exporter DaemonSet within the openshift-monitoring namespace includes a hardcoded "--collector.filesystem.mount-points-exclude" argument that excludes filesystem mount points matching certain patterns, including:
~~~

• --collector.filesystem.mount-points-exclude=^/(dev|proc|sys|run/k3s/containerd/.|var/lib/docker/.|var/lib/kubelet/pods/.+)($|/)
  ~~~
  This configuration is enforced and overwritten by the Cluster Monitoring Operator (CMO), making it impossible to modify via direct DaemonSet edits or the cluster-monitoring-config ConfigMap.

The enhancement request is to make this exclusion list configurable, either via the cluster-monitoring-config ConfigMap or another officially supported method, so that specific paths (like /var/lib/kubelet/pods/) can be included in metrics collection.

Customer wants to modify this argument and write it like this :
~~~
 - --collector.filesystem.mount-points-exclude=^/(dev|proc|sys|run/k3s/containerd/.|var/lib/docker/.)($|/)
~~~

3. Why Does the Customer Need This? (Business Requirements)

The customer is using CSI direct attached storage that is mounted under /var/lib/kubelet/pods/, and this path is currently being excluded from node-exporter metrics collection due to the default --collector.filesystem.mount-points-exclude regular expression.

As a result, latency and other performance metrics related to this critical storage subsystem are not being collected, limiting observability into key performance indicators for storage and application workloads.

By enabling configurability of this exclusion pattern, customers would be able to:

• Collect and monitor filesystem metrics from CSI volumes mounted under /var/lib/kubelet/pods/

• Improve observability into persistent storage performance

• Ensure full-stack monitoring coverage for storage-backed pods

• Meet SLAs and compliance requirements around storage monitoring

4. List Any Affected Packages or Components

• Cluster Monitoring Operator (CMO)

• Node Exporter

• ConfigMap: cluster-monitoring-config

• OpenShift Monitoring Stack