diff options
| author | markturansky <mturansk@redhat.com> | 2015-03-10 10:18:24 -0400 |
|---|---|---|
| committer | markturansky <mturansk@redhat.com> | 2015-03-10 10:18:24 -0400 |
| commit | 9249c265badd7e73f415fa8a539c4f6b9ed07b5a (patch) | |
| tree | 42c0ee759822be92c9149231c511b6640f2a79a3 /persistent-storage.md | |
| parent | f09c5510822ab57c0d08d1196fa7c4d24f0a0c37 (diff) | |
Added verbiage about events
Diffstat (limited to 'persistent-storage.md')
| -rw-r--r-- | persistent-storage.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/persistent-storage.md b/persistent-storage.md index a4c1c9ce..586f75bf 100644 --- a/persistent-storage.md +++ b/persistent-storage.md @@ -81,6 +81,13 @@ Scheduling constraints are to be handled similar to pod resource constraints. P TBD +#### Events + +The implementation of persistent storage will not require events to communicate to the user the state of their claim. The CLI for bound claims contains a reference to the backing persistent volume. This is always present in the API and CLI, making an event to communicate the same unnecessary. + +Events that communicate the state of a mounted volume are left to the volume plugins. + + ### Example #### Admin provisions storage |