Skip to content

Clarify usage of Service Account tokens and Dapr's secret management … #5013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
msfussell merged 2 commits into from
Jan 27, 2026
Merged

Clarify usage of Service Account tokens and Dapr's secret management … #5013

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fe82064
Clarify usage of Service Account tokens and Dapr's secret management …
MyMirelHub Jan 20, 2026
5552b68
Merge branch 'v1.16' into docs-clarification-on-ksa-automount-secrets
msfussell Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,7 +310,7 @@ It's recommended that you consider deploying your apps with `automountServiceAcc
Thus, Dapr does not set `automountServiceAccountToken: false` automatically for you. However, in all situations where the Service Account is not required by your solution, it's recommended that you set this option in the pods spec.

{{% alert title="Note" color="primary" %}}
Initializing Dapr components using [component secrets]({{% ref "component-secrets.md" %}}) stored as Kubernetes secrets does **not** require a Service Account token, so you can still set `automountServiceAccountToken: false` in this case. Only calling the Kubernetes secret store at runtime, using the [Secrets management]({{% ref "secrets-overview.md" %}}) building block, is impacted.
Initializing Dapr components using [component secrets]({{% ref "component-secrets.md" %}}) stored as Kubernetes secrets does **not** require your pod to have a Service Account token; the Dapr Operator resolves `secretKeyRef` at injection time. To run with `automountServiceAccountToken: false`, disable the sidecar's built-in Kubernetes secret store with the annotation `dapr.io/disable-builtin-k8s-secret-store: "true"`. Keep the secret store enabled (and mount a token) only if your app uses the runtime [Secrets management]({{% ref "secrets-overview.md" %}}) building block.
{{% /alert %}}

## Tracing and metrics configuration
Expand Down
Loading