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
You can expose additional TCP ports from your application. To learn more, see the [ingress concept article](ingress-overview.md#additional-tcp-ports).
151
151
152
-
> [Note]
153
-
> To use this preview feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
152
+
> [!NOTE]
153
+
> To use this feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
Copy file name to clipboardExpand all lines: articles/container-apps/ingress-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,12 +78,12 @@ With TCP ingress enabled, your container app:
78
78
- Is accessible to other container apps in the same environment via its name (defined by the `name` property in the Container Apps resource) and exposed port number.
79
79
- Is accessible externally via its fully qualified domain name (FQDN) and exposed port number if the ingress is set to "external".
In addition to the main HTTP/TCP port for your container apps, you might expose additional TCP ports to enable applications that accept TCP connections on multiple ports. This feature is in preview.
83
+
In addition to the main HTTP/TCP port for your container apps, you might expose additional TCP ports to enable applications that accept TCP connections on multiple ports.
84
84
85
85
> [!NOTE]
86
-
> As the feature is in preview, make sure you are using the latest preview version of the container apps CLI extension.
86
+
> This feature requires using the latest preview version of the container apps CLI extension.
87
87
88
88
The following apply to additional TCP ports:
89
89
- Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
0 commit comments