Skip to content

Commit 9c91a01

Browse files
committed
KEP-2485: Proposal and user stories
1 parent d023b09 commit 9c91a01

File tree

1 file changed

+28
-4
lines changed
  • keps/sig-storage/2485-read-write-once-pod-pv-access-mode

1 file changed

+28
-4
lines changed

keps/sig-storage/2485-read-write-once-pod-pv-access-mode/README.md

Lines changed: 28 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ tags, and then generate with `hack/update-toc.sh`.
8787
- [Non-Goals](#non-goals)
8888
- [Proposal](#proposal)
8989
- [User Stories (Optional)](#user-stories-optional)
90-
- [Story 1](#story-1)
91-
- [Story 2](#story-2)
90+
- [ReadWriteOncePod PVC Used Twice Fails for Second Consumer](#readwriteoncepod-pvc-used-twice-fails-for-second-consumer)
91+
- [ReadWriteOnce PVC Continues to Succeed with New Kubernetes, Old CSI Driver](#readwriteonce-pvc-continues-to-succeed-with-new-kubernetes-old-csi-driver)
9292
- [Notes/Constraints/Caveats (Optional)](#notesconstraintscaveats-optional)
9393
- [Risks and Mitigations](#risks-and-mitigations)
9494
- [Design Details](#design-details)
@@ -292,9 +292,33 @@ the system. The goal here is to make this feel real for users without getting
292292
bogged down.
293293
-->
294294

295-
#### Story 1
295+
#### ReadWriteOncePod PVC Used Twice Fails for Second Consumer
296296

297-
#### Story 2
297+
This scenario asserts a ReadWriteOncePod can only be bind mounted into a single
298+
pod on a single node.
299+
300+
- User creates a PVC with ReadWriteOncePod access mode
301+
- User creates pod 1 using this PVC, scheduled on node 1
302+
- User creates pod 2 using this PVC, also scheduled on node 1
303+
- User observes pod 2 fails to start because the referenced PVC is in-use by
304+
another pod on the same node
305+
306+
Additionally, for attachment:
307+
308+
- User creates pod 3 using this PVC, scheduled on node 2
309+
- User observes pod 3 fails to start because the referenced PVC is attached to
310+
another node
311+
312+
#### ReadWriteOnce PVC Continues to Succeed with New Kubernetes, Old CSI Driver
313+
314+
This scenario asserts the existing ReadWriteOnce behavior is preserved for old
315+
CSI drivers. The exact behavior may differ across CSI drivers since not all
316+
drivers conform to the CSI spec, but it should be consistent with how it behaved
317+
before.
318+
319+
- User creates a PVC with ReadWriteOnce access mode
320+
- User creates pod 1 using this PVC, scheduled on node 1
321+
- User observes pod running
298322

299323
### Notes/Constraints/Caveats (Optional)
300324

0 commit comments

Comments
 (0)