chore(rook-ceph): drop k8s-3 from the storage fleet for neptune's conversion

neptune is the last node to convert to bare metal, and its OSD drive is swapped in the same window. Removing k8s-3 from the explicit node list first means Rook stops managing that OSD before the drive it lives on goes away, rather than recreating it mid-reconcile and backfilling onto a disk that is about to be pulled. The device comment for k8s-3 goes with it: it described the PCI-passed-through drive that node saw as a Proxmox guest, which stops being true here. Ceph runs on two OSDs and size-3 pools stay degraded until the node rejoins. cephfs-metadata is already at 2/1 for exactly this window. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-26 00:47:52 +02:00
1 changed files with 4 additions and 7 deletions
@@ -167,10 +167,6 @@ spec:
  # impossible: the OSD is recreated within a reconcile and starts backfilling
  # onto the drive being replaced.
  #
-  # nvme0n1 on k8s-3 is the NVMe drive PCI-passed-through from neptune, and is
-  # the only block device that guest can see, so a bare device name is
-  # unambiguous there.
-  #
  # k8s-1 and k8s-2 are bare metal and see three NVMe drives each, so they name
  # their OSDs by /dev/disk/by-id path instead. A bare name would be actively
  # wrong: Talos enumerates these machines' drives in a different order than
@@ -192,9 +188,10 @@ spec:
    useAllNodes: false
    useAllDevices: false
    nodes:
-      - name: k8s-3
-        devices:
-          - name: nvme0n1
+      # k8s-3 is absent while neptune's OSD drive is swapped and the node is
+      # converted to bare metal. RE-ADD IT once the PM983 is in and the node has
+      # rejoined, naming the device by /dev/disk/by-id as the other two do —
+      # bare metal sees three NVMe drives and the bare name is not the OSD.
      - name: k8s-1
        devices:
          - fullpath: /dev/disk/by-id/nvme-SAMSUNG_MZQLB960HAJR-00007_S437NX0M400426