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/container-apps/services.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,17 +12,17 @@ ms.author: cshoe
12
12
# Connect to services in Azure Container Apps (preview)
13
13
14
14
> [!IMPORTANT]
15
-
> The public preview add-ons feature will be retired on September 30th, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for production-level service. For development and testing purposes, review the supported OSS quickstarts.
15
+
> The public preview add-ons feature will be retired on September 30, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for a production-level service. For development and testing purposes, review the supported open-source software (OSS) quickstarts.
16
16
17
17
As you develop applications in Azure Container Apps, you often need to connect to different services. Rather than creating services ahead of time and manually connecting them to your container app, you can quickly create instances of development-grade services that are designed for nonproduction environments known as add-ons.
18
18
19
-
Add-ons allow you to use OSS services without the burden of manual downloads, creation, and configuration. Since add-ons will be retired on September 30th, 2025, we recommend you use our new OSS quickstarts if you want to continue using these OSS services for nonproduction envrionments.
19
+
Add-ons allow you to use OSS services without the burden of manual downloads, creation, and configuration. Since add-ons will be retired on September 30, 2025, we recommend you use our new OSS quickstarts if you want to continue using these OSS services for nonproduction envrionments.
20
20
21
21
If you're ready for your app to use a production level service, you can connect your application to an Azure managed service.
22
22
23
23
## Migration Guide
24
24
25
-
As add-ons are being retired, you'll need to plan how to transition your applications away from this preview feature. Whether you're looking for a production level service or simply want to continue exploring open-source technologies in a dev/test capacity, the following steps will help you migrate smoothly.
25
+
As add-ons are being retired, you'll need to plan how to transition your applications away from this preview feature. Whether you're looking for a production level service or simply want to continue exploring opensource technologies in a dev/test capacity, the following steps will help you migrate smoothly.
26
26
27
27
Please note, you're responsible for data continuity between your add-on and your new Container App.
28
28
@@ -50,7 +50,7 @@ If you're ready for a production level service, follow these steps to transition
50
50
51
51
1. Create a new container app.
52
52
53
-
Create a new app using the [Azure Portal](quickstart-portal.md) or [CLI](get-started.md?tabs=bash).
53
+
Create a new app using the [Azure portal](quickstart-portal.md) or [CLI](get-started.md?tabs=bash).
54
54
55
55
1. Configure connection settings.
56
56
@@ -68,9 +68,9 @@ If you're ready for a production level service, follow these steps to transition
68
68
--resource-group <RESOURCE-GROUP>
69
69
```
70
70
71
-
### Option 2: Use open source images
71
+
### Option 2: Use open source quickstart images
72
72
73
-
If you only need these services for development or testing environments and do not require production-level guarantees, follow these steps to switch to use the open-source quickstart images:
73
+
If you only need these services for development or testing environments and don't require production-level guarantees, follow these steps to switch to use the open-source quickstart images.
74
74
75
75
1. Identify add-ons in use. Run the following command to locate all existing add-ons in your environment.
76
76
@@ -82,13 +82,13 @@ If you only need these services for development or testing environments and do n
82
82
--resource-group <RESOURCE_GROUP>
83
83
```
84
84
85
-
1. Review available quickstarts for Redis, PostgreSQL, MariaDB, Qdrant, and Kafka.
85
+
1. Review the supported quickstart images: Redis, PostgreSQL, MariaDB, Qdrant, and Kafka.
86
86
87
87
1. Plan data continuity.
88
88
89
89
Create a backup or snapshot of your data in the current add-on if applicable.
90
90
91
-
1. Create a new [Container App](quickstart-portal.md).
91
+
1. Create a new [Container App](quickstart-portal.md) using a quickstart image.
92
92
93
93
1. Remove the add-on.
94
94
@@ -105,7 +105,7 @@ If you only need these services for development or testing environments and do n
105
105
## Add-ons
106
106
107
107
> [!IMPORTANT]
108
-
> The public preview add-ons feature will be retired on September 30th, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for production-level service. For development and testing purposes, review the supported open-source quickstarts.
108
+
> The public preview add-ons feature will be retired on September 30, 2025. To prepare for this change, transition to Azure-managed services, such as Azure Cache for Redis or Azure Database for PostgreSQL for a production-level service. For development and testing purposes, review the supported open-source quickstarts.
109
109
110
110
Services available as an add-on include:
111
111
@@ -212,7 +212,7 @@ For more information on the service commands and arguments, see the
212
212
- Add-ons are in public preview.
213
213
- Any container app created before May 23, 2023 isn't eligible to use add-ons.
214
214
- Add-ons come with minimal guarantees. For instance, they're automatically restarted if they crash, however there's no formal quality of service or high-availability guarantees associated with them. For production workloads, use Azure-managed services.
215
-
- If you use your own VNET, you must use a workload profiles environment. The Add-ons feature is not supported in consumption only environments that use custom VNETs.
215
+
- If you use your own virtual network (VNET), you must use a workload profiles environment. The Add-ons feature isn't supported in consumption only environments that use custom VNETs.
0 commit comments