node-disk-manager icon indicating copy to clipboard operation
node-disk-manager copied to clipboard

Kubernetes Storage Device Management

Results 43 node-disk-manager issues
Sort by recently updated
recently updated
newest added

This is because some metrics can cause a performance impact and should be collected only at scheduled intervals.

Created as part of the review of https://github.com/openebs/node-disk-manager/pull/386 In the case of virtual disks, NDM creates a default partition on the device. At a later point if the user expands...

This helps as more devices are connected from on-prem setups, to identify their physical location.

There are several aspects of the code that can be refactored as listed below: - Move some of the code from /cmd folder into parent folder and keep the /cmd...

help wanted

Example: a single device being mounted in 2 nodes. (SAS Backends), or a network-attached device. In the current behavior, the last node that discovers a block device, will assume the...

**What happened**: I had a 3 node GKE cluster, with a single GPD attached to each node. Installed NDM from the `ndm-operator.yaml` in `v0.4.0` tag. Disks and BlockDevices were created...

enhancement

NDM DaemonSet pods use the ConfigMap to determine what disks are discovered and added as disk resources. This configuration is read at the startup by the DaemonSet Pods. **What is...

enhancement

Imagine a 2 node setup with following disks: **Node 1** * `/dev/sda`

enhancement

**What steps did you take and what happened:** During the initial install, there were two disks available for NDM to configure as block devices. Only one disk got configured, and...

enhancement
release-note/open