Bump repospawner to v0.1.1 (#446)

Why: repospawner v0.1.1 stops spawned job pods from automounting the API token.

- Bump the deployment image and the matching REPOSPAWNER_IMAGE env value to v0.1.1

Reviewed-on: #446
Co-authored-by: unkin-agent <unkin-agent@unkin.net>
Co-committed-by: unkin-agent <unkin-agent@unkin.net>
This commit was merged in pull request #446.
This commit is contained in:
2026-08-30 17:07:58 +10:00
committed by BenVincent
parent a9a66a07b1
commit c5fff07643
+2 -2
View File
@@ -31,7 +31,7 @@ spec:
type: RuntimeDefault
containers:
- name: repospawner
image: artifactapi.k8s.syd1.au.unkin.net/docker-internal/repospawner:v0.1.0
image: artifactapi.k8s.syd1.au.unkin.net/docker-internal/repospawner:v0.1.1
imagePullPolicy: IfNotPresent
ports:
- containerPort: 8080
@@ -43,7 +43,7 @@ spec:
# The server passes its own image down to the Jobs, so this must
# match the image above exactly.
- name: REPOSPAWNER_IMAGE
value: artifactapi.k8s.syd1.au.unkin.net/docker-internal/repospawner:v0.1.0
value: artifactapi.k8s.syd1.au.unkin.net/docker-internal/repospawner:v0.1.1
- name: REPOSPAWNER_JOB_SERVICE_ACCOUNT
value: repospawner
- name: GITEA_URL