Skip to content

Commit 22da62d

Browse files
Add pivots
1 parent 06223f5 commit 22da62d

File tree

2 files changed

+49
-8
lines changed

2 files changed

+49
-8
lines changed

articles/container-apps/workload-profiles-manage-cli.md

Lines changed: 40 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,16 @@ ms.service: container-apps
77
ms.topic: how-to
88
ms.date: 03/28/2023
99
ms.author: cshoe
10+
zone_pivot_groups: container-apps-vnet-types
1011
---
1112

13+
<!--
14+
::: zone pivot="aca-vnet-system"
15+
::: zone-end
16+
::: zone pivot="aca-vnet-custom"
17+
::: zone-end
18+
-->
19+
1220
# Manage workload profiles in a Consumption + Dedicated workload profiles plan structure (preview)
1321

1422
## Supported regions
@@ -24,18 +32,22 @@ The following regions support workload profiles during preview:
2432

2533
## Create a container app in a profile
2634

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
2840

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"
3442

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
3646

3747
Use the following commands to create an environment with a workload profile.
3848

49+
::: zone pivot="aca-vnet-custom"
50+
3951
1. Create a VNet
4052

4153
```bash
@@ -60,6 +72,8 @@ Use the following commands to create an environment with a workload profile.
6072

6173
Copy the ID value and paste into the next command.
6274

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+
6377
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:
6478
6579
- 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.
7084
|---|---|
7185
| 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. |
7286

87+
::: zone-end
88+
7389
1. Create *Consumption + Dedicated* environment with workload profile support
7490

7591
>[!Note]
@@ -88,6 +104,20 @@ Use the following commands to create an environment with a workload profile.
88104

89105
# [Internal environment](#tab/internal-env)
90106

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+
91121
```bash
92122
az containerapp env create \
93123
--enable-workload-profiles \
@@ -98,6 +128,8 @@ Use the following commands to create an environment with a workload profile.
98128
--internal--only
99129
```
100130

131+
::: zone-end
132+
101133
---
102134

103135
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.
125157
--workload-profile-name "Consumption"
126158
```
127159
128-
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).
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).
129161
130162
This command creates the new application in the environment using a specific workload profile.
131163

articles/zone-pivot-groups.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1888,6 +1888,15 @@ groups:
18881888
- id: aca-arm
18891889
title: Azure Resource Manager (ARM) template
18901890
# Owner: cshoe
1891+
- id: container-apps-vnet-types
1892+
title: Virtual network
1893+
prompt: Select a virtual network configuration
1894+
pivots:
1895+
- id: aca-vnet-system
1896+
title: System generated VNet
1897+
- id: aca-vnet-custom
1898+
title: Custom VNet
1899+
# Owner: cshoe
18911900
- id: container-apps-registry-types
18921901
title: Registry types
18931902
prompt: Select the type of container registry

0 commit comments

Comments
 (0)