rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Decrease indentation level for paragraph on credentials in git (#217) 

That paragraph belongs one level higher than it was, not being part of
the subsection on private Helm registries.
This commit is contained in:
Corentin Néau 2025-02-04 11:24:14 +01:00 committed by GitHub
parent 967aa30910
commit a51e4a1437
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/gitrepo-add.md
View File

@ -183,7 +183,7 @@ In the previous example credentials for username `user` will be used for the pat
If you are using ["rancher-backups"](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher) and want this secret to be included the backup, please add the label `resources.cattle.io/backup: true` to the secret. In that case, make sure to encrypt the backup to protect sensitive credentials. If you are using ["rancher-backups"](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher) and want this secret to be included the backup, please add the label `resources.cattle.io/backup: true` to the secret. In that case, make sure to encrypt the backup to protect sensitive credentials.
::: :::
### Storing Credentials in Git ## Storing Credentials in Git
It's recommended not to store credentials in Git. Even if the repository is properly protected, the secrets are at risk when cloning, etc. It's recommended not to store credentials in Git. Even if the repository is properly protected, the secrets are at risk when cloning, etc.
As a workaround tools like SOPS can be used to encrypt the credentials. As a workaround tools like SOPS can be used to encrypt the credentials.

2
versioned_docs/version-0.11/gitrepo-add.md
View File

@ -183,7 +183,7 @@ In the previous example credentials for username `user` will be used for the pat
If you are using ["rancher-backups"](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher) and want this secret to be included the backup, please add the label `resources.cattle.io/backup: true` to the secret. In that case, make sure to encrypt the backup to protect sensitive credentials. If you are using ["rancher-backups"](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher) and want this secret to be included the backup, please add the label `resources.cattle.io/backup: true` to the secret. In that case, make sure to encrypt the backup to protect sensitive credentials.
::: :::
### Storing Credentials in Git ## Storing Credentials in Git
It's recommended not to store credentials in Git. Even if the repository is properly protected, the secrets are at risk when cloning, etc. It's recommended not to store credentials in Git. Even if the repository is properly protected, the secrets are at risk when cloning, etc.
As a workaround tools like SOPS can be used to encrypt the credentials. As a workaround tools like SOPS can be used to encrypt the credentials.