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/workload-profiles-manage-cli.md
+40-8Lines changed: 40 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,16 @@ ms.service: container-apps
7
7
ms.topic: how-to
8
8
ms.date: 03/28/2023
9
9
ms.author: cshoe
10
+
zone_pivot_groups: container-apps-vnet-types
10
11
---
11
12
13
+
<!--
14
+
::: zone pivot="aca-vnet-system"
15
+
::: zone-end
16
+
::: zone pivot="aca-vnet-custom"
17
+
::: zone-end
18
+
-->
19
+
12
20
# Manage workload profiles in a Consumption + Dedicated workload profiles plan structure (preview)
13
21
14
22
## Supported regions
@@ -24,18 +32,22 @@ The following regions support workload profiles during preview:
24
32
25
33
## Create a container app in a profile
26
34
27
-
At a high level, when you create a container app into a workload profile, you go through the following steps:
35
+
::: zone pivot="aca-vnet-system"
36
+
37
+
System-generated VNet manages the complexity of running a virtual network for you, which means you don't have direct control over the VNet configuration. Without direction access to the configuration, you can't use [user defined routes](user-defined-routes.md). If you want to use user defined routes, you need to create a container apps environment with a custom VNet.
38
+
39
+
::: zone-end
28
40
29
-
- Select a workload profile
30
-
- Create or provide a VNet
31
-
- Create a subnet with a `Microsoft.App/environments` delegation (optional)
32
-
- Create a new environment
33
-
- Create a container app associated with the workload profile in the environment
41
+
::: zone pivot="aca-vnet-custom"
34
42
35
-
If you have an existing VNet, you can use it with the new environment you create. However, if you plan on using [user defined routes](user-defined-routes.md), then you need to create a new VNet.
43
+
When you create an environment with a custom VNet, you have full control over the VNet configuration. This amount of control gives you the option to implement [user defined routes](user-defined-routes.md) if necessary in your container app environment.
44
+
45
+
::: zone-end
36
46
37
47
Use the following commands to create an environment with a workload profile.
38
48
49
+
::: zone pivot="aca-vnet-custom"
50
+
39
51
1. Create a VNet
40
52
41
53
```bash
@@ -60,6 +72,8 @@ Use the following commands to create an environment with a workload profile.
60
72
61
73
Copy the ID value and paste into the next command.
62
74
75
+
The `Microsoft.App/environments` delegation is required to give the Container Apps runtime the needed control over your VNet to run workload profiles in the Container Apps environment.
76
+
63
77
You can specify as small as a `/27` CIDR (32 IPs-8 reserved) for the subnet. Some things to consider if you're going to specify a `/27` CIDR:
64
78
65
79
- There are 11 IP addresses reserved for Container Apps infrastructure. Therefore, a `/27` CIDR has a maximum of 21 IP available addresses.
@@ -70,6 +84,8 @@ Use the following commands to create an environment with a workload profile.
70
84
|---|---|
71
85
| Every replica requires one IP. Users can't have apps with more than 21 replicas across all apps. Zero downtime deployment requires double the IPs since the old revision is running until the new revision is successfully deployed. | Every instance (VM node) requires a single IP. You can have up to 21 instances across all workload profiles, and hundreds or more replicas running on these workload profiles. |
72
86
87
+
::: zone-end
88
+
73
89
1. Create *Consumption + Dedicated* environment with workload profile support
74
90
75
91
>[!Note]
@@ -88,6 +104,20 @@ Use the following commands to create an environment with a workload profile.
88
104
89
105
# [Internal environment](#tab/internal-env)
90
106
107
+
::: zone pivot="aca-vnet-system"
108
+
109
+
```bash
110
+
az containerapp env create \
111
+
--enable-workload-profiles \
112
+
--resource-group "<RESOURCE_GROUP>" \
113
+
--name "<NAME>" \
114
+
--location "<LOCATION>"
115
+
```
116
+
117
+
::: zone-end
118
+
119
+
::: zone pivot="aca-vnet-custom"
120
+
91
121
```bash
92
122
az containerapp env create \
93
123
--enable-workload-profiles \
@@ -98,6 +128,8 @@ Use the following commands to create an environment with a workload profile.
98
128
--internal--only
99
129
```
100
130
131
+
::: zone-end
132
+
101
133
---
102
134
103
135
This command can take up to 10 minutes to complete.
@@ -125,7 +157,7 @@ Use the following commands to create an environment with a workload profile.
125
157
--workload-profile-name "Consumption"
126
158
```
127
159
128
-
This command deploys the application to the builtin Consumption workload profile. If you want to create an app in a dedicated workload profile, you first need to [add the profile to the environment](#add-profiles).
160
+
This command deploys the application to the built-in Consumption workload profile. If you want to create an app in a dedicated workload profile, you first need to [add the profile to the environment](#add-profiles).
129
161
130
162
This command creates the new application in the environment using a specific workload profile.
0 commit comments