#686 clarify when values should be raw or manually base64 encoded (#761)

* 686 clarify when values should be raw or manually base64 encoded

* rm'd section as duplicate of https://ranchermanager.docs.rancher.com/reference-guides/backup-restore-configuration/backup-configuration#example-credentialsecret

* UI instructions for finding Backup: Create + link to how-to on secret creation

* sync language

* Apply suggestions from code review

Co-authored-by: Billy Tat <btat@suse.com>

---------

Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Marty Hernandez Avedon
2023-09-13 16:29:07 -04:00
committed by GitHub
co-authored by Billy Tat
parent 58d3cc3f17
commit ef5ab63ddd
2 changed files with 6 additions and 16 deletions
@@ -242,19 +242,6 @@ spec:
encryptionConfigSecretName: test-encryptionconfig
```
## Example Credential Secret for Storing Backups in S3
```yaml
apiVersion: v1
kind: Secret
metadata:
name: creds
type: Opaque
data:
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
## Example EncryptionConfiguration
The snippet below demonstrates two different types of secrets and their relevance with respect to Backup and Restore of custom resources.