This message was deleted.

I am pretty sure it’s all just done via annotations on the Kubernetes objects. See https://github.com/longhorn/longhorn/blob/master/enhancements/20200319-default-disks-and-node-configuration.md

This is not help my requirement. Does longhorn has self brain to check the node to find out new disk (lets say if we added new disk to existing node and we can not add new disk in longhorn every time like running CLI/API in fat clusters).

longhorn doesn’t use raw physical disks. If you add raw disk, you need to either format it, mount it to a path, and then configure LH to use that path, or add the new disk to an existing array/volume group/etc, and then expand the filesystem to make the additional space available to LH.