You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -3,21 +3,19 @@ title: Dapr extension for Azure Kubernetes Service (AKS) overview
3
3
description: Learn more about using Dapr on your Azure Kubernetes Service (AKS) cluster to develop applications.
4
4
ms.author: nickoman
5
5
ms.topic: article
6
-
ms.date: 03/28/2024
6
+
ms.date: 04/22/2024
7
7
---
8
8
9
9
# Dapr
10
10
11
-
[Distributed Application Runtime (Dapr)][dapr-docs] offers APIs that help you write and implement simple, portable, resilient, and secured microservices. Running as a sidecar process in tandem with your applications, Dapr APIs abstract away common complexities you may encounter when building distributed applications, such as:
11
+
[Distributed Application Runtime (Dapr)][dapr-docs] offers APIs that help you write and implement simple, portable, resilient, and secured microservices. Dapr APIs run as a sidecar process in tandem with your applications and abstract away common complexities you may encounter when building distributed applications, such as:
12
12
- Service discovery
13
13
- Message broker integration
14
14
- Encryption
15
15
- Observability
16
16
- Secret management
17
17
18
-
Dapr is incrementally adoptable. You can use any of the API building blocks as needed.
19
-
20
-
:::image type="content" source="./media/dapr-overview/dapr-building-blocks.png" alt-text="Diagram showing how many different code frameworks can interface with the various building blocks of Dapr via HTTP or gRPC." lightbox="./media/dapr-overview/dapr-building-blocks.png":::
18
+
Dapr is incrementally adoptable. You can use any of the API building blocks as needed. [Learn the support level Microsoft offers for each Dapr API and component.](#currently-supported)
21
19
22
20
## Capabilities and features
23
21
@@ -36,15 +34,113 @@ Dapr provides the following set of capabilities to help with your microservice d
36
34
- Reliable, secure, and resilient service-to-service calls through HTTP and gRPC APIs
37
35
- Publish and subscribe messaging made easy with support for CloudEvent filtering and “at-least-once” semantics for message delivery
38
36
- Pluggable observability and monitoring through Open Telemetry API collector
39
-
- Works independent of language, while also offering language specific SDKs
40
-
- Integration with VS Code through the Dapr extension
37
+
- Works independent of language, while also offering language specific software development kits (SDKs)
38
+
- Integration with Visual Studio Code through the Dapr extension
41
39
-[More APIs for solving distributed application challenges][dapr-blocks]
42
40
41
+
## Currently supported
42
+
43
+
The Dapr extension is the only Microsoft-supported option for Dapr in AKS.
44
+
45
+
### Issue handling
46
+
47
+
Microsoft categorizes issues raised against the Dapr extension into two parts:
48
+
- Extension operations
49
+
- Dapr runtime (including APIs and components)
50
+
51
+
The following table breaks down support priority levels for each of these categories.
|**Extension operations**| Issues encountered during extension operations, such as installing/uninstalling or upgrading the Dapr extension. | Microsoft prioritizes for immediate resolution. | Microsoft investigates and addresses as needed. |
56
+
|**Dapr runtime**| Issues encountered when using the Dapr runtime, APIs, and components via the extension. | Microsoft works with the open source community to investigate high priority issues. Depending on priority, severity, and size of the issue, Microsoft either resolves them directly in the extension, or works with the Dapr open source project to resolve in a hotfix or future Dapr open source release. Once fixes are released in Dapr open source, they are then made available in the Dapr extension. | Microsoft investigates new functional issues alongside the Dapr open source project and collaborates with them to resolve in a hotfix or future Dapr open source release. Known open source functional issues won't be investigated by Microsoft at this time. |
57
+
58
+
### Dapr versions
59
+
60
+
Microsoft provides best-effort support for [the latest version of Dapr and two previous versions (N-2)][dapr-supported-version]. The latest patch version is the only supported version of each minor version release. Currently, the Dapr extension for AKS or Arc-enabled Kubernetes supports the following Dapr versions:
61
+
62
+
- 1.13.x
63
+
- 1.12.x
64
+
- 1.11.x
65
+
66
+
The Dapr extension support varies depending on how you manage the runtime.
67
+
68
+
#### Self-managed
69
+
Self-managed runtime requires manual upgrade to remain in the support window. To upgrade Dapr via the extension, follow the [Update extension instance](deploy-extensions-az-cli.md#update-extension-instance) instructions.
70
+
71
+
After a Dapr runtime version reaches end of Microsoft support, your applications continue to run unchanged. However, Microsoft can no longer provide security patches or related customer support for that runtime version. If your application encounters any problems past the end-of-support date for that version, we recommend upgrading to a supported version to receive the latest security patches and features.
72
+
73
+
#### Auto-upgrade
74
+
Enabling auto-upgrade requires careful consideration. While auto-upgrade keeps your Dapr extension updated to the latest minor version, you may experience breaking changes between updates. Microsoft isn't responsible for any downtime caused due to breaking changes between auto-updates.
75
+
76
+
### Components and APIs
77
+
78
+
You can use all Dapr components and APIs via the Dapr extension, including those in [alpha and beta status][dapr-alpha-beta]. However, Microsoft only provides support to a subset of APIs and components, following the [defined issue handling policies](#issue-handling).
79
+
80
+
#### Stable Dapr APIs
81
+
82
+
The Dapr extension supports stable versions of Dapr APIs (building blocks).
|[**Service-to-service invocation**][dapr-serviceinvo]| Stable | Discover services and perform reliable, direct service-to-service calls with automatic mTLS authentication and encryption.(#limitations) |
87
+
|[**State management**][dapr-statemgmt]| Stable | Provides state management capabilities for transactions and CRUD operations. |
88
+
|[**Pub/sub**][dapr-pubsub]| Stable | Allows publisher and subscriber apps to intercommunicate via an intermediary message broker. You can also create [declarative subscriptions][dapr-subscriptions] to a topic using an external component JSON file. |
89
+
|[**Bindings**][dapr-bindings]| Stable | Trigger your applications based on events. |
90
+
|[**Actors**][dapr-actors]| Stable | Dapr actors are message-driven, single-threaded, units of work designed to quickly scale. For example, in burst-heavy workload situations. |
91
+
|[**Observability**][dapr-observability]| Stable | Send tracing information to an Application Insights backend. |
92
+
|[**Secrets**][dapr-secrets]| Stable | Access secrets from your application code or reference secure values in your Dapr components. |
93
+
|[**Configuration**][dapr-config]| Stable | Retrieve and subscribe to application configuration items for supported configuration. stores. |
A: Where a service mesh is defined as a networking service mesh, Dapr is not a service mesh. While Dapr and service meshes do offer some overlapping capabilities, a service mesh is focused on networking concerns, whereas Dapr is focused on providing building blocks that make it easier for developers to build applications as microservices. Dapr is developer-centric, while service meshes are infrastructure-centric.
143
+
A: Where a service mesh is defined as a networking service mesh, Dapr isn't a service mesh. While Dapr and service meshes do offer some overlapping capabilities, a service mesh is focused on networking concerns, whereas Dapr is focused on providing building blocks that make it easier for developers to build applications as microservices. Dapr is developer-centric, while service meshes are infrastructure-centric.
48
144
49
145
Some common capabilities that Dapr shares with service meshes include:
50
146
@@ -53,13 +149,17 @@ Some common capabilities that Dapr shares with service meshes include:
53
149
- Service-to-service distributed tracing
54
150
- Resiliency through retries
55
151
56
-
In addition, Dapr provides other application-level building blocks for state management, pub/sub messaging, actors, and more. However, Dapr does not provide capabilities for traffic behavior such as routing or traffic splitting. If your solution would benefit from the traffic splitting a service mesh provides, consider using [Open Service Mesh][osm-docs].
152
+
In addition, Dapr provides other application-level building blocks for state management, pub/sub messaging, actors, and more. However, Dapr doesn't provide capabilities for traffic behavior such as routing or traffic splitting. If your solution would benefit from the traffic splitting a service mesh provides, consider using [Open Service Mesh][osm-docs].
57
153
58
154
For more information on Dapr and service meshes, and how they can be used together, visit the [Dapr documentation][dapr-docs].
59
155
60
156
### How does the Dapr secrets API compare to the Secrets Store CSI driver?
61
157
62
-
Both the Dapr secrets API and the managed Secrets Store CSI driver allow for the integration of secrets held in an external store, abstracting secret store technology from application code. The Secrets Store CSI driver mounts secrets held in Azure Key Vault as a CSI volume for consumption by an application. Dapr exposes secrets via a RESTful API that can be called by application code and can be configured with assorted secret stores. The following table lists the capabilities of each offering:
158
+
Both the Dapr secrets API and the managed Secrets Store CSI driver allow for the integration of secrets held in an external store, abstracting secret store technology from application code. The Secrets Store CSI driver mounts secrets held in Azure Key Vault as a CSI volume for consumption by an application. Dapr exposes secrets via a RESTful API that can be:
159
+
- Called by application code
160
+
- Configured with assorted secret stores
161
+
162
+
The following table lists the capabilities of each offering:
63
163
64
164
|| Dapr secrets API | Secrets Store CSI driver |
65
165
| --- | --- | ---|
@@ -68,19 +168,19 @@ Both the Dapr secrets API and the managed Secrets Store CSI driver allow for the
68
168
|**Secret rotation**| New API calls obtain the updated secrets | Polls for secrets and updates the mount at a configurable interval |
69
169
|**Logging and metrics**| The Dapr sidecar generates logs, which can be configured with collectors such as Azure Monitor, emits metrics via Prometheus, and exposes an HTTP endpoint for health checks | Emits driver and Azure Key Vault provider metrics via Prometheus |
70
170
71
-
For more information on the secret management in Dapr, see the [secrets management building block overview][dapr-secrets-block].
171
+
For more information on the secret management in Dapr, see the [secrets management overview][dapr-secrets].
72
172
73
173
For more information on the Secrets Store CSI driver and Azure Key Vault provider, see the [Secrets Store CSI driver overview][csi-secrets-store].
74
174
75
175
### How does the managed Dapr cluster extension compare to the open source Dapr offering?
76
176
77
177
The managed Dapr cluster extension is the easiest method to provision Dapr on an AKS cluster. With the extension, you're able to offload management of the Dapr runtime version by opting into automatic upgrades. Additionally, the extension installs Dapr with smart defaults (for example, provisioning the Dapr control plane in high availability mode).
78
178
79
-
When installing Dapr OSS via helm or the Dapr CLI, runtime versions and configuration options are the responsibility of developers and cluster maintainers.
179
+
When installing Dapr open source via helm or the Dapr CLI, developers and cluster maintainers are also responsible for runtime versions and configuration options.
80
180
81
181
Lastly, the Dapr extension is an extension of AKS, therefore you can expect the same support policy as other AKS features.
82
182
83
-
[Learn more about migrating from Dapr OSS to the Dapr extension for AKS][dapr-migration].
183
+
[Learn more about migrating from Dapr open source to the Dapr extension for AKS][dapr-migration].
0 commit comments