Skip to content

Commit

Permalink
- Clarify change to default behavior
Browse files Browse the repository at this point in the history
- Add note on restarting pods during change of flag
  • Loading branch information
RaunakShah committed Jan 31, 2022
1 parent 9c1b720 commit 5419cd9
Showing 1 changed file with 7 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -417,7 +417,10 @@ unauthorized conversion of the volume mode.
- Describe the mechanism: Out-of-tree flag named `PreventVolumeModeConversion`,
which will be enabled in `external-provisioner` and `external-snapshotter`.
- Will enabling / disabling the feature require downtime of the control
plane? No
plane? `external-provisioner` and `external-snapshotter` will need to be
restarted for the changes to take effect. This means that there will be a few
seconds of downtime until the newer Pods are Running. There will not be any
effect on the previously running applications.
- Will enabling / disabling the feature require downtime or reprovisioning
of a node? (Do not assume `Dynamic Kubelet Config` feature is enabled).
No
Expand All @@ -428,6 +431,9 @@ Yes. Users without requisite privileges cannot alter the volume mode of `VolumeS
when it is being used to create a `PVC`. Users with privileges need to add an
annotation to the corresponding `VolumeSnapshotContent` instance if they
require the volume mode to be converted.
The default behavior does not make any validations prior to provisioning a volume.
The volume mode can be converted by any user when a `PVC` is created from a
`VolumeSnapshot`.
###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?
Expand Down

0 comments on commit 5419cd9

Please sign in to comment.