|
2 | 2 | ## ex: https://github.com/myorg/myrepo or https://github.com/myorg
|
3 | 3 | githubConfigUrl: ""
|
4 | 4 |
|
5 |
| -## githubConfigSecret is the k8s secrets to use when auth with GitHub API. |
6 |
| -## You can choose to use GitHub App or a PAT token |
| 5 | +## githubConfigSecret is the k8s secret information to use when authenticating via the GitHub API. |
| 6 | +## You can choose to supply: |
| 7 | +## A) a PAT token, |
| 8 | +## B) a GitHub App, or |
| 9 | +## C) a pre-defined Kubernetes secret. |
| 10 | +## The syntax for each of these variations is documented below. |
| 11 | +## (Variation A) When using a PAT token, the syntax is as follows: |
7 | 12 | githubConfigSecret:
|
8 |
| - ### GitHub Apps Configuration |
9 |
| - ## NOTE: IDs MUST be strings, use quotes |
10 |
| - #github_app_id: "" |
11 |
| - #github_app_installation_id: "" |
12 |
| - #github_app_private_key: | |
13 |
| - |
14 |
| - ### GitHub PAT Configuration |
15 |
| - github_token: "" |
16 |
| -## If you have a pre-define Kubernetes secret in the same namespace the gha-runner-scale-set is going to deploy, |
17 |
| -## you can also reference it via `githubConfigSecret: pre-defined-secret`. |
18 |
| -## You need to make sure your predefined secret has all the required secret data set properly. |
| 13 | + # Example: |
| 14 | + # github_token: "ghp_sampleSampleSampleSampleSampleSample" |
| 15 | + github_token: "" |
| 16 | +# |
| 17 | +## (Variation B) When using a GitHub App, the syntax is as follows: |
| 18 | +# githubConfigSecret: |
| 19 | +# # NOTE: IDs MUST be strings, use quotes |
| 20 | +# github_app_id: "" |
| 21 | +# github_app_installation_id: "" |
| 22 | +# github_app_private_key: | |
| 23 | +# private key line 1 |
| 24 | +# private key line 2 |
| 25 | +# . |
| 26 | +# . |
| 27 | +# . |
| 28 | +# private key line N |
| 29 | +# |
| 30 | +## (Variation C) When using a pre-defined Kubernetes secret in the same namespace that the gha-runner-scale-set is going to deploy, |
| 31 | +## the syntax is as follows: |
| 32 | +# githubConfigSecret: pre-defined-secret |
| 33 | +## Notes on using pre-defined Kubernetes secrets: |
| 34 | +## You need to make sure your predefined secret has all the required secret data set properly. |
19 | 35 | ## For a pre-defined secret using GitHub PAT, the secret needs to be created like this:
|
20 | 36 | ## > kubectl create secret generic pre-defined-secret --namespace=my_namespace --from-literal=github_token='ghp_your_pat'
|
21 | 37 | ## For a pre-defined secret using GitHub App, the secret needs to be created like this:
|
22 | 38 | ## > kubectl create secret generic pre-defined-secret --namespace=my_namespace --from-literal=github_app_id=123456 --from-literal=github_app_installation_id=654321 --from-literal=github_app_private_key='-----BEGIN CERTIFICATE-----*******'
|
23 |
| -# githubConfigSecret: pre-defined-secret |
24 | 39 |
|
25 | 40 | ## proxy can be used to define proxy settings that will be used by the
|
26 | 41 | ## controller, the listener and the runner of this scale set.
|
|
0 commit comments