dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify that disabling kubernetes built in secret store can only be done with an annotation, not by setting a helm argument (#4124) 

Clarify that disabling kubernetes built in secret store can only be done with an annotation, not by setting a helm argument

Signed-off-by: james-bartlett <jamesmbartlett@outlook.com>
This commit is contained in:
james-bartlett 2024-05-02 14:55:15 -05:00 committed by GitHub
parent a107511779
commit 0bfa02bc5d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-overview.md
View File

@ -41,7 +41,7 @@ Applications can also use the secrets API to access secrets from a Kubernetes se
- The Helm defaults, or
- `dapr init -k`
If you are using another secret store, you can disable (not configure) the Dapr Kubernetes secret store by setting `disable-builtin-k8s-secret-store` to `true` through the Helm settings. The default is `false`.
If you are using another secret store, you can disable (not configure) the Dapr Kubernetes secret store by adding the annotation `dapr.io/disable-builtin-k8s-secret-store: "true"` to the deployment.yaml file. The default is `false`.
In the example below, the application retrieves the same secret "mysecret" from a Kubernetes secret store.
@ -86,4 +86,4 @@ Want to skip the quickstarts? Not a problem. You can try out the secret manageme
## Next steps
- Learn [how to use secret scoping]({{< ref secrets-scopes.md >}}).
- Read the [secrets API reference doc]({{< ref secrets_api.md >}}).
- Read the [secrets API reference doc]({{< ref secrets_api.md >}}).