Overview of Dapr on Kubernetes

    Dapr can be configured to run on any supported versions of Kubernetes. To achieve this, Dapr begins by deploying the , dapr-operator, , and dapr-sentry Kubernetes services. These provide first-class integration to make running applications with Dapr easy.

    • dapr-operator: Manages component updates and Kubernetes services endpoints for Dapr (state stores, pub/subs, etc.)
    • dapr-sidecar-injector: Injects Dapr into deployment pods and adds the environment variables and DAPR_GRPC_PORT to enable user-defined applications to easily communicate with Dapr without hard-coding Dapr port values.
    • dapr-sentry: Manages mTLS between services and acts as a certificate authority. For more information read the security overview.

    Deploying Dapr to a Kubernetes cluster

    Deploying and running a Dapr enabled application into your Kubernetes cluster is as simple as adding a few annotations to the pods schema. To give your service an and port known to Dapr, turn on tracing through configuration and launch the Dapr sidecar container, you annotate your Kubernetes pod like this. For more information check dapr annotations

    Pulling container images from private registries

    Dapr works seamlessly with any user application container image, regardless of its origin. Simply init Dapr and add the Dapr annotations to your Kubernetes definition to add the Dapr sidecar.

    For information about pulling your application images from a private registry, reference the . If you are using Azure Container Registry with Azure Kubernetes Service, reference the AKS documentation.

    You can see some examples in the Kubernetes getting started quickstart.

    Supported versions