NDM daemon runs in containers and has to access the underlying storage devices and run in Privileged mode. NDM daemonset discovers the disks on each node and creates a custom resource called Block Device or BD. NDM is deployed as a daemonset during installation of OpenEBS. In spite of doing all of the above, NDM contributes to overall ease of provisioning persistent volumes. Allow dynamically attaching/detaching disks to a storage pod, without restarting the corresponding NDM pod running on the Node where the disk is attached/detached.Predict failures on the Disks to help with taking preventive actions.Easy to access inventory of Block Devices available across the Kubernetes Cluster.These custom resources are aimed towards helping hyper-converged Storage Operators by providing abilities like: It is a daemonset which runs on each node, detects attached block devices based on the filters and loads them as block devices custom resource into Kubernetes. NDM treats block devices as resources that need to be monitored and managed just like other resources such as CPU, Memory and Network. Node Disk Manager(NDM) is an important component in the OpenEBS architecture.

Ndm flooring