The documentation you are viewing is for Dapr v1.11 which is an older version of Dapr. For up-to-date documentation, see the latest version.
The purpose of this component is to load the Kubernetes secret named after the key name.
NoteThis component uses the cryptographic engine in Dapr to perform operations. Although keys are never exposed to your application, Dapr has access to the raw key material.
crypto.yaml component file has the following structure:
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> spec: type: crypto.dapr.kubernetes.secrets version: v1 metadata:
WarningThe above example uses secrets as plain strings. It is recommended to use a secret store for the secrets, as described here.
Spec metadata fields
For the Kubernetes secret store component, there are no metadata attributes.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.