diff options
| author | Mayank Kumar <mayank.kumar@salesforce.com> | 2018-03-27 23:39:46 -0700 |
|---|---|---|
| committer | Mayank Kumar <mayank.kumar@salesforce.com> | 2018-03-27 23:39:46 -0700 |
| commit | 0d49718ea5046cefcc18a7802c51d8ed1060e364 (patch) | |
| tree | 5b978465631e0e827408d5b27d026579bccd3ba8 | |
| parent | 61a13fab66d7ef4038dd6f514d9e467636e3688c (diff) | |
add a section on upgrade downgrade
| -rw-r--r-- | contributors/design-proposals/storage/pv-to-rbd-mapping.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/contributors/design-proposals/storage/pv-to-rbd-mapping.md b/contributors/design-proposals/storage/pv-to-rbd-mapping.md index be775525..a64a1018 100644 --- a/contributors/design-proposals/storage/pv-to-rbd-mapping.md +++ b/contributors/design-proposals/storage/pv-to-rbd-mapping.md @@ -69,6 +69,18 @@ and hence can accommodate any pvc names and namespaces which are stored as arbit It also leaves room for storing any other metadata about the PVC. +### Upgrade/Downgrade Behavior + +#### Upgrading from a K8s version without this metadata to a version with this metadata +The metadata for image is populated on CreateImage. After an upgrade, existing RBD Images will not have that +metadata set. When the next AttachDisk happens, we can check if the metadata is not set, set it. Cluster +administrators could also run a one time script to set this manually. For all newly created RBD images, +the rbd image metadata will be set properly. + +#### Downgrade from a K8s version with this metadata to a version without this metadata +After a downgrade, all existing RBD images will have the metadata set. New RBD images created after the +downgrade will not have this metadata. + ## Proposal 1 Make the RBD Image name as base64 encoded PVC name(namespace+name) |