Skip to content

fix(arc): enable SA token automount on arc-tf runner pods#33

Merged
xnoto merged 1 commit intomainfrom
fix/arc-tf-token-automount
Apr 30, 2026
Merged

fix(arc): enable SA token automount on arc-tf runner pods#33
xnoto merged 1 commit intomainfrom
fix/arc-tf-token-automount

Conversation

@xnoto
Copy link
Copy Markdown
Contributor

@xnoto xnoto commented Apr 30, 2026

Summary

The arc-tf-runner SA is now wired and ArgoCD propagates it to the runner template, but the in-cluster kubectl patch step still fails with the server has asked for the client to provide credentials. The chart's default automountServiceAccountToken: false means the SA's projected token never reaches the runner container.

Setting automountServiceAccountToken: true on the runner template spec mounts the token at /var/run/secrets/kubernetes.io/serviceaccount/token so kubectl can authenticate.

Test plan

  • After ArgoCD syncs, kubectl -n arc-runners get pod -o jsonpath='{..volumes[?(@.name=="kube-api-access-*")].name}' shows the projected token volume
  • Push to main triggers Sync ArgoCD job and successfully patches the bootstrap Applications

🤖 Generated with Claude Code

The gha-runner-scale-set chart defaults automountServiceAccountToken
to false, so the arc-tf-runner SA's token never reached the runner
container and kubectl failed with 401. Set it true on the template
spec so the projected token is mounted at the standard path and
in-cluster auth works.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@xnoto xnoto self-assigned this Apr 30, 2026
@xnoto xnoto merged commit f9ffff1 into main Apr 30, 2026
2 checks passed
@xnoto xnoto deleted the fix/arc-tf-token-automount branch April 30, 2026 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant