diff options
| author | Cheng Xing <cxing@google.com> | 2017-08-29 19:43:42 -0700 |
|---|---|---|
| committer | Cheng Xing <cxing@google.com> | 2017-09-01 15:47:39 -0700 |
| commit | a1ad98ffe9ada93d3ca0185bc799052e9cffbae5 (patch) | |
| tree | ba8ef9d677517323f9524e1569ea606d5ed4156e | |
| parent | 1886e7a6e25b4002d71dc3f81890ab0424d97d30 (diff) | |
Added comments about possible driver actions
| -rw-r--r-- | contributors/design-proposals/flexvolume-deployment.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/contributors/design-proposals/flexvolume-deployment.md b/contributors/design-proposals/flexvolume-deployment.md index 6e4e3881..07f75904 100644 --- a/contributors/design-proposals/flexvolume-deployment.md +++ b/contributors/design-proposals/flexvolume-deployment.md @@ -19,6 +19,7 @@ An automated deployment technique is discussed in [Recommended Driver Deployment When there is a modification of the driver directory, a notification is sent to the filesystem watch from kubelet or controller manager. When kubelet or controller-manager searches for plugins (such as when a volume needs to be mounted), if there is a signal from the watch, it probes the driver directory and loads currently installed drivers as volume plugins. +The modification can be a driver install (addition), upgrade/downgrade (update), or uninstall (deletion). If a volume depends on an existing driver, it can be *updated* but not *deleted*. ## **Detailed Design** |