Skip to content

Commit 835ccd9

Browse files
committed
add networking to WP page
1 parent c0fad4e commit 835ccd9

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/container-apps/workload-profiles-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,10 @@ The availability of different workload profiles varies by region.
6464

6565
You can constrain the memory and CPU usage of each app inside a workload profile, and you can run multiple apps inside a single instance of a workload profile. However, the total amount of resources available to a container app is less than what's allocated to a profile. The difference between allocated and available resources is what's reserved for the Azure Container Apps runtime.
6666

67+
## Networking
68+
69+
When using workload profiles in the Consumption + Dedicated plan structure, additional networking features to fully secure your ingress/egress networking traffic such as user defined routes are available. To learn more on how to secure your network with Container Apps, see [lock down your Container App environment](./networking.md#lock-down-your-container-app-environment).
70+
6771
## Scaling
6872

6973
When demand for new apps or more replicas of an existing app exceeds the profile's current resources, profile instances may be added. Inversely, if the number of apps or replicas goes down, profile instances may be removed. You have control over the constraints on the minimum and maximum number of profile instances. Azure calculates [billing](billing.md#consumption-dedicated) largely based on the number of running profile instances.

0 commit comments

Comments
 (0)