Skip to content

Commit e777911

Browse files
Merge pull request #264763 from cachai2/AdditionalTCPPortsGA
update ingress overview and how to
2 parents 05ad85b + cd32af7 commit e777911

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/container-apps/ingress-how-to.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -145,12 +145,12 @@ Disable ingress for your container app by omitting the `ingress` configuration p
145145

146146
::: zone-end
147147

148-
## <a name="use-additional-tcp-ports"></a>Use additional TCP ports (preview)
148+
## <a name="use-additional-tcp-ports"></a>Use additional TCP ports
149149

150150
You can expose additional TCP ports from your application. To learn more, see the [ingress concept article](ingress-overview.md#additional-tcp-ports).
151151

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.
154154
155155

156156
::: zone pivot="azure-cli"

articles/container-apps/ingress-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -78,12 +78,12 @@ With TCP ingress enabled, your container app:
7878
- 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.
7979
- Is accessible externally via its fully qualified domain name (FQDN) and exposed port number if the ingress is set to "external".
8080

81-
## <a name="additional-tcp-ports"></a>Additional TCP ports (preview)
81+
## <a name="additional-tcp-ports"></a>Additional TCP ports
8282

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. 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.
8484

8585
> [!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.
8787
8888
The following apply to additional TCP ports:
8989
- 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

Comments
 (0)