fix(stand): register Node CRDs + use LOOPFILE so DRBD has block dev

Two issues blocked multi-replica DRBD scenarios on the dev stand:

1) blockstor Node CRDs were never created. The satellite's c-r
   ResourceReconciler lists Node CRDs to resolve peer addresses
   for the .res file's `on <node> { address ... }` blocks — with
   an empty Node list, peer addresses fell through to 0.0.0.0 and
   drbdadm could never establish the replication connection.
   install-blockstor.sh now iterates k8s worker nodes and creates
   one blockstor Node CRD per worker with NetInterfaces.Address
   taken from the k8s InternalIP.

2) The "stand" pool used providerKind: FILE_THIN which hands back
   a raw file path (`/var/lib/blockstor-pool/<rd>_<vol>.img`).
   drbdmeta rejects that with `not a block device`. Switch to
   LOOPFILE — same backing files, same dir, but the provider
   wraps each one with `losetup --find --show` so the .res file
   gets a /dev/loopN that DRBD can attach. losetup --find uses
   /dev/loop-control under the hood, so this scales to ~hundreds
   of loops without hardcoding numbers.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>

Author: kvaps

stand/blockstor-storagepools.yaml

@@ -28,7 +28,7 @@ metadata:
 spec:
   nodeName: __WORKER_1__
   poolName: stand
-  providerKind: FILE_THIN
+  providerKind: LOOPFILE
   props:
     StorDriver/FileDir: /var/lib/blockstor-pool
 ---
@@ -39,7 +39,7 @@ metadata:
 spec:
   nodeName: __WORKER_2__
   poolName: stand
-  providerKind: FILE_THIN
+  providerKind: LOOPFILE
   props:
     StorDriver/FileDir: /var/lib/blockstor-pool
 ---
@@ -50,7 +50,7 @@ metadata:
 spec:
   nodeName: __WORKER_3__
   poolName: stand
-  providerKind: FILE_THIN
+  providerKind: LOOPFILE
   props:
     StorDriver/FileDir: /var/lib/blockstor-pool
 ---

stand/install-blockstor.sh

@@ -63,4 +63,23 @@ if [[ "$ready" != "3" ]]; then
     exit 1
 fi
 
+# Bootstrap blockstor Node CRDs from k8s worker nodes so the
+# satellite reconciler's peer-resolution path has an address per
+# node — otherwise multi-replica .res files render a 0.0.0.0
+# placeholder for any peer this satellite hasn't directly seen.
+# Cluster-scoped CRD; metadata.name == k8s node name.
+echo ">> register blockstor Node CRDs from k8s workers"
+for node in $(kubectl get nodes -l '!node-role.kubernetes.io/control-plane' -o jsonpath='{.items[*].metadata.name}'); do
+    ip=$(kubectl get node "$node" -o jsonpath='{.status.addresses[?(@.type=="InternalIP")].address}')
+    cat <<EOF | kubectl apply -f -
+apiVersion: blockstor.io.blockstor.io/v1alpha1
+kind: Node
+metadata: {name: $node}
+spec:
+  type: SATELLITE
+  netInterfaces:
+    - {name: default, address: $ip}
+EOF
+done
+
 echo ">> blockstor stack ready on $(basename "$WORK_DIR")"