It looks like there’s a replica still in the

running

state:

NAME                                                  STATE     NODE        DISK                                   INSTANCEMANAGER                                       IMAGE                                    AGE
pvc-f04941e1-6181-40ec-9dd4-a0da45337b0b-r-02dff950   stopped   k3s-sd-02   7b8edb0b-be57-445a-a46a-b51f9d4108fc                                                                                                  27h
pvc-e98b8f1f-be78-4f4c-ad89-c5dacff9b944-r-7802ebd8   stopped   k3s-sd-02   7b8edb0b-be57-445a-a46a-b51f9d4108fc                                                                                                  27h
pvc-f04941e1-6181-40ec-9dd4-a0da45337b0b-r-e8f3a25f   stopped   k3s-sd-03   2a123a1a-e5d5-4ff2-9792-47681f0de058                                                                                                  27h
pvc-f04941e1-6181-40ec-9dd4-a0da45337b0b-r-b7cd708f   stopped   k3s-sd-02   7b8edb0b-be57-445a-a46a-b51f9d4108fc                                                                                                  19h
pvc-e98b8f1f-be78-4f4c-ad89-c5dacff9b944-r-1b84d377   stopped   k3s-sd-03   2a123a1a-e5d5-4ff2-9792-47681f0de058                                                                                                  27h
pvc-f04941e1-6181-40ec-9dd4-a0da45337b0b-r-87243b29   running   k3s-sd-03   2a123a1a-e5d5-4ff2-9792-47681f0de058   instance-manager-r-a12ca5e95c05a4540f1c4927edf6e26c   longhornio/longhorn-engine:master-head   19h
pvc-f04941e1-6181-40ec-9dd4-a0da45337b0b-r-63c3c5b6   unknown   k3s-sd-01   ed2f0682-4140-41a6-b96d-f2d5e0eb4562   instance-manager-r-9a6b35fa67bbad2fe7f184ae87ea6659   longhornio/longhorn-engine:master-head   23h

But again, there’s no instance-manager running.