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
Copy file name to clipboardExpand all lines: articles/aks/dapr-overview.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.date: 04/22/2024
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. [Learn the support level Microsoft offers for each Dapr API and component.](#components-and-apis)
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)
19
19
20
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":::
21
21
@@ -47,26 +47,24 @@ The following table breaks down support priority levels for each of these catego
|**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. |
50
-
|**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 immediately 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. |
50
+
|**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. |
51
51
52
52
### Dapr versions
53
53
54
-
The Dapr extension support varies depending on how you manage the runtime.
54
+
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:
55
55
56
-
**Self-managed**
57
-
For self-managed runtime, 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.
56
+
- 1.13.x
57
+
- 1.12.x
58
+
- 1.11.x
58
59
59
-
Currently, the Dapr extension for AKS or Arc-enabled Kubernetes supports the following Dapr versions:
60
-
61
-
- 1.13.2
62
-
- 1.12.4
63
-
- 1.11.6*
64
-
65
-
_*This version will be retired once the next Dapr version is released._
60
+
The Dapr extension support varies depending on how you manage the runtime.
66
61
62
+
#### Self-managed
67
63
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.
68
64
69
-
**Auto-upgrade**
65
+
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.
66
+
67
+
#### Auto-upgrade
70
68
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.
Copy file name to clipboardExpand all lines: includes/dapr-in-azure/dapr-support-policy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ ms.author: hannahhunter
9
9
10
10
A subset of Dapr components is supported for the Dapr extension for AKS and Arc-enabled Kubernetes. Within that subset, Dapr components are broken into two support categories: Tier 1 or Tier 2.
11
11
12
-
-[Tier 1 components:](../../articles/aks/dapr-overview.md#tier-1-components) Stable components that receive immediate investigation in critical (security or serious regression) scenarios. Otherwise, collaborate with open source to address in a hotfix or the next regular release.
13
-
-[Tier 2 components:](../../articles/aks/dapr-overview.md#tier-2-components) Components that receive immediate investigation and are supported with best effort attempt to address with third party provider.
12
+
-[Tier 1 components:](../../articles/aks/dapr-overview.md#tier-1-components) Stable components that receive immediate investigation in critical (security or serious regression) scenarios. Otherwise, Microsoft collaborates with open source to address in a hotfix or the next regular release.
13
+
-[Tier 2 components:](../../articles/aks/dapr-overview.md#tier-2-components) Components that are investigated on a lesser priority with a third party provider.
0 commit comments