diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-09-01 15:54:11 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-01 15:54:11 -0700 |
| commit | d57a2a5d6f493488ea66b028c4cd14b5930e9bfb (patch) | |
| tree | aa50cfe2f6ccdc314c579dc87758eb507edbed03 | |
| parent | f421f6b290057c2cb7705ca746883f3097d61f26 (diff) | |
| parent | a1ad98ffe9ada93d3ca0185bc799052e9cffbae5 (diff) | |
Merge pull request #997 from verult/flexdeploy
Automatic merge from submit-queue
Flexvolume Dynamic Plugin Discovery: Added comments about possible driver installation actions
Made it explicit that driver uninstalls are allowed, and cautioned against uninstalling while a volume depends on the driver.
/sig storage
/assign @chakri-nelluri @saad-ali
| -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** |
