Merge pull request #248543 from cachai2/additionalPorts

additionalPorts

Author: Stacyrch140

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

@@ -162,6 +162,100 @@ Disable ingress for your container app by omitting the `ingress` configuration p
 
 ::: zone-end
 
+## <a name="use-additional-tcp-ports"></a>Use additional TCP ports (preview)
+
+You can expose additional TCP ports from your application. To learn more, see the [ingress concept article](ingress-overview.md#additional-tcp-ports).
+
+
+::: zone pivot="azure-cli"
+
+# [Azure CLI](#tab/azure-cli)
+
+Adding additional TCP ports can be done through the CLI by referencing a YAML file with your TCP port configurations.
+
+```azurecli
+az containerapp update 
+    --name <app-name> \
+    --resource-group <resource-group> \
+    --yaml <your-yaml-file>
+```
+
+The following is an example YAML file you can reference in the above CLI command. The configuration for the additional TCP ports is under `additionalPortMappings`.
+
+```yml
+location: northcentralus
+name: multiport-example
+properties:
+  configuration:
+    activeRevisionsMode: Single
+    ingress:
+      additionalPortMappings:
+      - exposedPort: 21025
+        external: true
+        targetPort: 1025
+      allowInsecure: false
+      external: true
+      targetPort: 1080
+      traffic:
+      - latestRevision: true
+        weight: 100
+      transport: http
+  managedEnvironmentId: <env id>
+  template:
+    containers:
+    - image: maildev/maildev
+      name: maildev
+      resources:
+        cpu: 0.25
+        memory: 0.5Gi
+    scale:
+      maxReplicas: 1
+      minReplicas: 1
+  workloadProfileName: Consumption
+type: Microsoft.App/containerApps
+```
+
+::: zone-end
+
+::: zone pivot="azure-portal"
+
+# [Portal](#tab/portal)
+
+This feature is not supported in the Azure portal.
+
+::: zone-end
+
+::: zone pivot="azure-resource-manager"
+
+# [ARM template](#tab/arm-template)
+
+The following ARM template provides an example of how you can add additional ports to your container apps. Each additional port should be added under `additionalPortMappings` within the `ingress` section for `configuration` within `properties` for the container app. The following is an example:
+
+```json
+{
+  ...
+  "properties": {
+    ...
+    "configuration": {
+      "ingress": {
+        ...
+        "additionalPortMappings": [
+          {
+            "external": false
+            "targetPort": 80
+            "exposedPort": 12000
+          }
+        ]
+      }
+    }
+  ...
+}
+```
+
+---
+
+::: zone-end
+
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/container-apps/ingress-overview.md

@@ -64,7 +64,7 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 | `X-Forwarded-Proto` | Protocol used by the client to connect with the Container Apps service. | `http` or `https` |
 | `X-Forwarded-For` | The IP address of the client that sent the request. |  |
 | `X-Forwarded-Host` | The host name the client used to connect with the Container Apps service. |  |
-| `X-Forwarded-Client-Cert` | The client certificate if `clientCertificateMode` is set. | Semicolon seperated list of Hash, Cert, and Chain. For example: `Hash=....;Cert="...";Chain="...";` |
+| `X-Forwarded-Client-Cert` | The client certificate if `clientCertificateMode` is set. | Semicolon separated list of Hash, Cert, and Chain. For example: `Hash=....;Cert="...";Chain="...";` |
 
 ### <a name="tcp"></a>TCP
 
@@ -78,11 +78,25 @@ With TCP ingress enabled, your container app:
 - 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.
 - Is accessible externally via its fully qualified domain name (FQDN) and exposed port number if the ingress is set to "external".
 
+## <a name="additional-tcp-ports"></a>Additional TCP ports (preview)
+
+In addition to the main HTTP/TCP port for your container apps, you may expose additional TCP ports to enable applications that accept TCP connections on multiple ports. This feature is in preview.
+
+The following apply to additional TCP ports:
+- Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
+- Any externally exposed additional TCP ports must be unique across the entire Container Apps environment. This includes all external additional TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the additional ports are internal, the same port can be shared by multiple apps.
+- If an exposed port is not provided, the exposed port will default to match the target port.
+- Each target port must be unique, and the same target port cannot be exposed on different exposed ports.
+- There is a maximum of 5 additional ports per app. If additional ports are required, please open a support request.
+- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the additional TCP ports, these built-in features are not supported.
+
+Visit the [how to article on ingress](ingress-how-to.md#use-additional-tcp-ports) for more information on how to enable additional ports for your container apps.
+
 ## Domain names
 
 You can access your app in the following ways:
 
-- The default fully-qualified domain name (FQDN):  Each app in a Container Apps environment is automatically assigned an FQDN based on the environment's DNS suffix. To customize an environment's DNS suffix, see [Custom environment DNS Suffix](environment-custom-dns-suffix.md).
+- The default fully qualified domain name (FQDN):  Each app in a Container Apps environment is automatically assigned an FQDN based on the environment's DNS suffix. To customize an environment's DNS suffix, see [Custom environment DNS Suffix](environment-custom-dns-suffix.md).
 - A custom domain name:  You can configure a custom DNS domain for your Container Apps environment.  For more information, see [Custom domain names and certificates](./custom-domains-certificates.md).
 - The app name: You can use the app name for communication between apps in the same environment.