public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Make explicit Secret data is base64-encoded

Browse Source
This commit is contained in:
Billy Tat
2021-10-05 15:49:47 -07:00
parent cba255379c
commit 0769ffa254
6 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.5/en/backups/configuration/backup-config/_index.md
+3 -3
View File
@@ -136,8 +136,8 @@ metadata:
name: creds
type: Opaque
data:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
### IAM Permissions for EC2 Nodes to Access S3
@@ -183,4 +183,4 @@ After the role is created, and you have attached the corresponding instance prof
# Examples
For example Backup custom resources, refer to [this page.](../../examples/#backup)
For example Backup custom resources, refer to [this page.](../../examples/#backup)
content/rancher/v2.5/en/backups/examples/_index.md
+2 -2
View File
@@ -269,8 +269,8 @@ metadata:
name: creds
type: Opaque
data:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
# Example EncryptionConfiguration
content/rancher/v2.5/en/backups/migrating-rancher/_index.md
+2 -2
View File
@@ -39,8 +39,8 @@ metadata:
name: s3-creds
type: Opaque
stringData:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
This secret can be created in any namespace, with the above example it will get created in the default namespace
content/rancher/v2.6/en/backups/configuration/backup-config/_index.md
+3 -3
View File
@@ -126,8 +126,8 @@ metadata:
name: creds
type: Opaque
data:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
### IAM Permissions for EC2 Nodes to Access S3
@@ -173,4 +173,4 @@ After the role is created, and you have attached the corresponding instance prof
# Examples
For example Backup custom resources, refer to [this page.](../../examples/#backup)
For example Backup custom resources, refer to [this page.](../../examples/#backup)
content/rancher/v2.6/en/backups/examples/_index.md
+2 -2
View File
@@ -266,8 +266,8 @@ metadata:
name: creds
type: Opaque
data:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
# Example EncryptionConfiguration
content/rancher/v2.6/en/backups/migrating-rancher/_index.md
+2 -2
View File
@@ -37,8 +37,8 @@ metadata:
name: s3-creds
type: Opaque
stringData:
accessKey: <Enter your access key>
secretKey: <Enter your secret key>
accessKey: <Enter your base64-encoded access key>
secretKey: <Enter your base64-encoded secret key>
```
This secret can be created in any namespace, with the above example it will get created in the default namespace