eclipse-che
Docs: Warn about PVC multi-attach errors when using per-user storage strategy on a multi-node cluster
Is your task related to a problem? Please describe
When using the per-user PVC strategy in a multi-node cluster, it's possible for user workspaces to be scheduled on a node in the cluster that is not the node where the PVC was provisioned. If other workspaces are currently bound to the PVC, then workspaces created on these other nodes will fail to startup. This is due to the fact that PVCs are provisioned with the ReadWriteOnce access mode, meaning only a single node can be bound to the PVC at a time.
Describe the solution you'd like
I think we should make a note/warning about this in the configuring the storage strategy page of the docs to warn users about this potential pitfall of using the per-user storage strategy. The workaround is for users to opt for the per-workspace storage strategy if they need storage on a multinode cluster.
Describe alternatives you've considered
No response
Additional context
Customers are encountering this issue with the per-user storage strategy, and I haven't found mention of this pitfall with the per-user storage strategy in our docs.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
