Skip to content

Commit 55ceb14

Browse files
Merge pull request #292199 from craigshoemaker/aca/jason/automatic-port-detection
[Container Apps] Update: Ingress -> automatic port detection (Jason)
2 parents ac923d1 + a8d8b69 commit 55ceb14

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

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

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: how-to
8-
ms.date: 06/13/2024
8+
ms.date: 01/17/2024
99
ms.author: cshoe
1010
ms.custom: devx-track-azurecli
1111
zone_pivot_groups: arm-azure-cli-portal
@@ -28,10 +28,16 @@ You can set the following ingress template properties:
2828
| `external` | Allow ingress to your app from outside its Container Apps environment. |`true` or `false`(default) | Yes |
2929
| `ipSecurityRestrictions` | IP ingress restrictions. See [Set up IP ingress restrictions](ip-restrictions.md) | An array of rules | No |
3030
| `stickySessions.affinity` | Enables [session affinity](sticky-sessions.md). | `none` (default), `sticky` | No |
31-
| `targetPort` | The port your container listens to for incoming requests. | Set this value to the port number that your container uses. For HTTP ingress, your application ingress endpoint is always exposed on port `443`. | Yes |
31+
| `targetPort` | The port your container app listens to for incoming requests. | Set this value to the port number that your container app uses. For HTTP ingress, your application ingress endpoint is always exposed on port `443`. | Yes |
3232
| `traffic` | [Traffic splitting](traffic-splitting.md) weights split between revisions. | An array of rules | No |
3333
| `transport` | The transport protocol type. | auto (default) detects HTTP/1 or HTTP/2, `http` for HTTP/1, `http2` for HTTP/2, `tcp` for TCP. | No |
3434

35+
### Automatic port detection
36+
37+
If your container app has HTTP ingress enabled and you have not set a target port, Azure Container Apps will automatically detect the target port by scanning all listening ports on your container. If there is only one port detected, that port will be set as the target port for your container app. If there is more than 1 port detected, the container app will not automatically set the target port, and you will need to set the target port manually.
38+
39+
- Automatic port detection only works for HTTP traffic, not TCP traffic.
40+
- If you have HTTP health probes listening on ports 80 or 443, this can interfere with automatic port detection. The default ingress configuration uses TCP health probes. For more information see [health probes](health-probes.md).
3541

3642
## Enable ingress
3743

0 commit comments

Comments
 (0)