From 2f3fa9699fd2b7c273f916525f93ea4345e79730 Mon Sep 17 00:00:00 2001 From: Anshul Ahuja Date: Tue, 14 Feb 2023 16:49:35 +0530 Subject: [PATCH] Spelling fix Signed-off-by: Anshul Ahuja --- design/multiple-csi-volumesnapshotclass-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/multiple-csi-volumesnapshotclass-support.md b/design/multiple-csi-volumesnapshotclass-support.md index f3879374a..9f8507beb 100644 --- a/design/multiple-csi-volumesnapshotclass-support.md +++ b/design/multiple-csi-volumesnapshotclass-support.md @@ -46,7 +46,7 @@ The Velero CSI plugin chooses the VolumeSnapshotClass in the cluster that has th ## Scenario 2 - Bob is a cluster admin has PVCs storing different types of data. -- Most of the PVCs are used for storing non senstive application data. But certain PVCs store critical financial data. +- Most of the PVCs are used for storing non-sensitive application data. But certain PVCs store critical financial data. - For such PVCs Bob wants to use a VolumeSnapshotClass with certain encryption related parameters set. - In current velero, Bob can't achieve this as the CSI plugin will use the default VolumeSnapshotClass for the driver and all snapshots will be taken using the same VolumeSnapshotClass. - Proposed design will allow Bob to achieve this by overriding the VolumeSnapshotClass to use for a particular driver and backup/schedule using annotations on those specific PVCs.