argoproj / argoproj/argo-workflows

Remove `automountServiceAccountToken` for main containers

Open
#7,970 7 comments 12 reactions 0 assignees View on GitHub
area/executor type/security
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

There's no reason to have this mounted for most tasks. In fact, main containers will get `pod patch` allowing the to change other pods within the namespace.

This might be easier than fixing #3961

Note, you now must explicitly mount the service account token, which has unpredicatable name.

# Use Cases

Better default security.

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Argo Workflows constructs pods and handles automountServiceAccountToken for main containers. Read issue #3961 and Kubernetes service-account-token mounting behavior, then verify that automatic tokens are removed while explicit token mounts remain usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.