Configuration

Change the behavior of Dapr sidecars or globally on Dapr system services

Dapr configurations are settings that enable you to change both the behavior of individual Dapr applications, or the global behavior of the system services in the Dapr control plane.

Configurations are defined and deployed as a YAML file. An application configuration example is like this:

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Configuration
  3. metadata:
  4.   name: daprConfig
  5.   namespace: default
  6. spec:
  7.   tracing:
  8.     samplingRate: "1"
  9.     zipkin:
  10.       endpointAddress: "http://localhost:9411/api/v2/spans"

This configuration configures tracing for telemetry recording. It can be loaded in self-hosted mode by editing the default configuration file called config.yaml file in your .dapr directory, or by applying it to your Kubernetes cluster with kubectl/helm.

Read this page for a list of all configuration options.

Last modified September 20, 2021 : Merge pull request #1800 from greenie-msft/gRPC_proxying_video (36dff3c)