fix CI runner secrets: correct Gitea URL and use Vault-backed tokens
The ExternalSecret had a stale Gitea URL (192.168.8.148:30322 — old local IP) and runner tokens were never populated in Vault. Update the template URL to the cluster-internal Gitea service DNS, and store the registration tokens in Vault at secret/gitea.runner_token.
This commit is contained in:
@@ -17,7 +17,7 @@ spec:
|
|||||||
creationPolicy: Owner
|
creationPolicy: Owner
|
||||||
template:
|
template:
|
||||||
data:
|
data:
|
||||||
GITEA_INSTANCE_URL: "http://192.168.8.148:30322"
|
GITEA_INSTANCE_URL: "http://gitea.git.svc.cluster.local:3000"
|
||||||
GITEA_RUNNER_REGISTRATION_TOKEN: "{{ .runner_token }}"
|
GITEA_RUNNER_REGISTRATION_TOKEN: "{{ .runner_token }}"
|
||||||
data:
|
data:
|
||||||
- secretKey: runner_token
|
- secretKey: runner_token
|
||||||
@@ -41,7 +41,7 @@ spec:
|
|||||||
creationPolicy: Owner
|
creationPolicy: Owner
|
||||||
template:
|
template:
|
||||||
data:
|
data:
|
||||||
GITEA_INSTANCE_URL: "http://192.168.8.148:30322"
|
GITEA_INSTANCE_URL: "http://gitea.git.svc.cluster.local:3000"
|
||||||
GITEA_RUNNER_REGISTRATION_TOKEN: "{{ .runner_token }}"
|
GITEA_RUNNER_REGISTRATION_TOKEN: "{{ .runner_token }}"
|
||||||
data:
|
data:
|
||||||
- secretKey: runner_token
|
- secretKey: runner_token
|
||||||
|
|||||||
Reference in New Issue
Block a user