This message was deleted.

Try to use best-effort storage locality ?

already using best effort

oof. Even with best-effort, longhorn will mount remote volumes if it can't find a node with both storage and ressources available. i wish 'strict-local' would let us have multiple replicas AND fail pods when it can't find a suitable node

But my question is about how notified when the volumes get re-mounted in read-only mode

https://longhorn.io/docs/1.6.1/monitoring/metrics/ doesnt looks like it's even an exposed metric

Thanks. That's very useful. I think I got it working OK. Looks like the

LonghornVolumeStatus

alerts might be useful.

hi! I've opened an issue for this... https://github.com/longhorn/longhorn/issues/8508