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

Clarify requirements on token-based auth (#334) 

Github and BitBucket are special cases, now supported.
This commit is contained in:
Corentin Néau 2025-09-25 11:50:31 +02:00 committed by GitHub
parent 8f4e03a7c7
commit f7cacfa771
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/gitrepo-add.md
View File

@ -158,6 +158,9 @@ Just like with SSH, reference the secret in your GitRepo resource via `clientSec
branch: main
clientSecretName: basic-auth-secret
:::info
When using BitBucket and access tokens, the username must be `x-token-auth`.
:::
### Using Custom CA Bundles

2
docs/troubleshooting.md
View File

@ -165,7 +165,7 @@ done ; wait
When testing Fleet with private git repositories, you will notice that HTTP secrets are no longer supported in Github. To work around this issue, follow these steps:
1. Create a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) in Github.
1. In Rancher, create an HTTP [secret](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets) with your Github username.
1. In Rancher, create an HTTP [secret](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets) with your Github personal access token. Your username is optional.
1. Use your token as the secret.
### Fleet fails with bad response code: 403