Skip to content

Commit 04f00d5

Browse files
committed
Address latest comments
1 parent 9af1df6 commit 04f00d5

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/en/blog/_posts/2022-05-18-prevent-unauthorised-volume-mode-conversion.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,9 @@ It is upto the cluster administrator to provide these rights only to trusted use
4343
or applications, like backup vendors.
4444

4545
If the alpha feature is [enabled](https://kubernetes-csi.github.io/docs/) in
46-
`snapshot-controller` and `external-provisioner`, then unauthorised users will
47-
not be allowed to modify the volume mode of a PVC when it is being created from
48-
a `VolumeSnapshot`.
46+
`snapshot-controller`, `snapshot-validation-webhook` and `external-provisioner`,
47+
then unauthorised users will not be allowed to modify the volume mode of a PVC
48+
when it is being created from a `VolumeSnapshot`.
4949

5050
To convert the volume mode, an authorised user must do the following:
5151

@@ -98,8 +98,8 @@ spec:
9898
Repeat steps 1 to 3 for all `VolumeSnapshotContents` whose volume mode needs to be
9999
converted during a backup or restore operation.
100100

101-
If the above annotation is present on a `VolumeSnapshotContent` object,
102-
Kubernetes will not prevent the volume mode from being converted.
101+
If the annotation shown in step 4 above is present on a `VolumeSnapshotContent`
102+
object, Kubernetes will not prevent the volume mode from being converted.
103103
Users should keep this in mind before they attempt to add the annotation
104104
to any `VolumeSnapshotContent`.
105105

0 commit comments

Comments
 (0)