feat: configurable service account and SA token mount for runner pods #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/sa-token-mount"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add serviceAccountName and automountServiceAccountToken fields to
KubernetesBackendSpec. Automount defaults to true so runner pods get
a service account token, enabling workflow steps to authenticate to
cluster services like OpenBao.
When privileged (DinD) mode is enabled, the generated runner config
now bind-mounts the SA token into workflow containers so they can
also access it.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.15.0 | Safety Check | anthropic | tracking id
r-c75c13-e9c556This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — No obvious security vulnerabilities or bugs found; the automated credential detections are false positives related to legitimate Kubernetes service account token handling.
Complexity: moderate
Safety Check Review
Automated Alerts Review
The automated observations flagged "possible secret or credential detected" in multiple files. Upon examination, these are all legitimate references to Kubernetes service account tokens:
/var/run/secrets/kubernetes.io/serviceaccountServiceAccountNameandAutomountServiceAccountTokenCode Analysis
No alarming issues found.