From 0ab0391f560340fa926b9a7a025eaa06303e38af Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 19 Apr 2022 10:46:55 +0530 Subject: [PATCH] Update content/rancher/v2.6/en/backups/examples/_index.md Co-authored-by: Jen Travinski --- content/rancher/v2.6/en/backups/examples/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/backups/examples/_index.md b/content/rancher/v2.6/en/backups/examples/_index.md index a6922f9c802..4670c938ef1 100644 --- a/content/rancher/v2.6/en/backups/examples/_index.md +++ b/content/rancher/v2.6/en/backups/examples/_index.md @@ -276,7 +276,7 @@ The snippet below demonstrates two different types of secrets and their relevanc The first example is that of a secret that is used to encrypt the backup files. The backup operator, in this case, will not be able to read the secrets encryption file. It only uses the contents of the secret. -The second example is that of a Kubernetes secrets encryption config file that is used to encrypt secrets when stored in etcd. It is important to note that while backing up your etcd config ensure you also backup your EncryptionConfiguration. Failing to do so might result in you not being able to use the restored data. +The second example is that of a Kubernetes secrets encryption config file that is used to encrypt secrets when stored in etcd. **While backing up your etcd config, be sure to also backup your EncryptionConfiguration.** Failing to do so might result in you not being able to use the restored data. ```yaml