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
@@ -106,7 +112,6 @@ This rule may generate false positive results for stateful applications.
106
112
107
113
## LINKS
108
114
109
-
-[Avoid a requirement to store server-side session state](https://learn.microsoft.com/azure/well-architected/scalability/performance-efficiency#implementation)
@@ -14,14 +15,15 @@ Limit inbound communication for Container Apps is limited to callers within the
14
15
15
16
## DESCRIPTION
16
17
17
-
Container apps allows you to expose your container app to the Internet, your VNET, or to other container apps within the same environment by enabling ingress.
18
+
Inbound access to a Container App is configured by enabling ingress.
19
+
Container Apps can be configured to allow external ingress or not.
20
+
External ingress permits communication outside the Container App environment from a private VNET or the Internet.
21
+
To restrict communication to a private VNET your Container App Environment must be:
18
22
19
-
When inbound access to the app is required, configure the ingress.
20
-
Applications that do batch processing or consume events may not require ingress to be enabled.
21
-
22
-
When external ingress is configured, communication outside the container apps environment is enabled from your private VNET or the Internet.
23
-
To restrict communication to a private VNET your Container App Environment must be deployed on a custom VNET with an Internal load balancer.
23
+
- Configured with a custom VNET.
24
+
- Configured with an internal load balancer.
24
25
26
+
Applications that do batch processing or consume events may not require ingress to be enabled.
25
27
If communication outside your Container Apps Environment is not required, disable external ingress.
0 commit comments