From 98cd5108a382cb6cf9fda054bd61ff95ba33bb9c Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Mon, 11 Apr 2022 11:33:37 +0530 Subject: [PATCH 1/4] Amending Encryption Configuration Section --- content/rancher/v2.6/en/backups/examples/_index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/rancher/v2.6/en/backups/examples/_index.md b/content/rancher/v2.6/en/backups/examples/_index.md index 87c607b7780..38aa7964541 100644 --- a/content/rancher/v2.6/en/backups/examples/_index.md +++ b/content/rancher/v2.6/en/backups/examples/_index.md @@ -272,6 +272,13 @@ data: # Example EncryptionConfiguration +The snippet below demonstrates two different types of secrets and their relevance with respect to Backup and Restore of custom resources.s + +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. + + ```yaml apiVersion: apiserver.config.k8s.io/v1 kind: EncryptionConfiguration From b20990affbfe93d03db1c23c93445300c05d8440 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 12 Apr 2022 11:46:58 +0530 Subject: [PATCH 2/4] Update content/rancher/v2.6/en/backups/examples/_index.md Co-authored-by: Brad Davidson --- 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 38aa7964541..a6922f9c802 100644 --- a/content/rancher/v2.6/en/backups/examples/_index.md +++ b/content/rancher/v2.6/en/backups/examples/_index.md @@ -272,7 +272,7 @@ data: # Example EncryptionConfiguration -The snippet below demonstrates two different types of secrets and their relevance with respect to Backup and Restore of custom resources.s +The snippet below demonstrates two different types of secrets and their relevance with respect to Backup and Restore of custom resources. 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. From 0ab0391f560340fa926b9a7a025eaa06303e38af Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 19 Apr 2022 10:46:55 +0530 Subject: [PATCH 3/4] 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 From 8defd30bccffbd46c12c8f16462497b73b9432d4 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Wed, 27 Apr 2022 20:18:18 +0530 Subject: [PATCH 4/4] Update content/rancher/v2.6/en/backups/examples/_index.md Co-authored-by: Brad Davidson --- 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 4670c938ef1..b1282f9c3ca 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. **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. +The second example is that of a Kubernetes secrets encryption config file that is used to encrypt secrets when stored in etcd. **When backing up the etcd datastore, be sure to also back up the EncryptionConfiguration.** Failure to do so will result in an inability to use the restored data if secrets encryption was in use at the time the data was backed up. ```yaml