Jan Šafránek

> But, in absence of the attacher sidecar, RWO backward compatibility looks to be broken! That said, RWO volumes can get mounted on more than one node at same time...

cc @chrishenzie

> From my understanding, we're asking if we can enforce this for non-attachable volumes? e.g. during volume mount we'd need to detect this was already mounted on another node? I...

/retitle RWO access mode should be enforced for non-attachable volumes There is no "Backward Compatibliity broken" here, non-attachable RWO volumes always had the same (bad) behavior.

BTW, this looks like a dup of https://github.com/kubernetes/kubernetes/issues/103305 /close

/ok-to-test

/lgtm /approve

I think it's caused by https://github.com/aws/efs-utils/issues/125 - the race can result in a timeout / failure or in very rare cases it could IMO surface as efs-utils using the same...

@lemosric have you considered https://github.com/aws/efs-utils/pull/129 ?

/remove-lifecycle stale