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
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/how-to-configure-ingress.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,14 +17,14 @@ This article shows you how to set and update an application's ingress settings i
17
17
18
18
The Azure Spring Apps service uses an underlying ingress controller to handle application traffic management. The following ingress settings are supported for customization.
19
19
20
-
| Name | Ingress setting | Default value | Valid range | Description |
|`ingress-read-timeout`|`proxy-read-timeout`| 300 |\[1,1800\]| The timeout in seconds for reading a response from a proxied server. |
23
-
|`ingress-send-timeout`|`proxy-send-timeout`| 60 |\[1,1800\]| The timeout in seconds for transmitting a request to the proxied server. |
24
-
|`session-affinity`|`affinity`| None | Session, None| The type of the affinity that makes the request come to the same pod replica that was responding to the previous request. Set `session-affinity` to Cookie to enable session affinity. In the portal only, you must choose the enable session affinity box. |
25
-
|`session-max-age`|`session-cookie-max-age`| 0 |\[0, 604800\]| The time in seconds until the cookie expires, corresponding to the `Max-Age` cookie directive. If you set `session-max-age` to 0, the expiration period is equal to the browser session period. |
26
-
|`backend-protocol`|`backend-protocol`| Default | Default, GRPC(short for Remote Procedure Call) | Sets the backend protocol to indicate how NGINX should communicate with the backend service. Default means HTTP/HTTPS/WebSocket. The `backend-protocol` setting only applies to client-to-app traffic. For app-to-app traffic within the same service instance, choose any protocol for app-to-app traffic without modifying the `backend-protocol` setting. The protocol doesn't restrict your choice of protocol for app-to-app traffic within the same service instance.|
27
-
|`client-auth`|`client-auth`| 0 selected | - | Select the certificates with public key you uploaded in TLS/SSL settings, and ingress concats these certificates to one and use it for client authentication.|
20
+
| Name | Ingress setting | Default value | Valid range | Description|
|`ingress-read-timeout`|`proxy-read-timeout`| 300 |\[1,1800\]| The timeout in seconds for reading a response from a proxied server. |
23
+
|`ingress-send-timeout`|`proxy-send-timeout`| 60 |\[1,1800\]| The timeout in seconds for transmitting a request to the proxied server. |
24
+
|`session-affinity`|`affinity`| None |`Session`, `None`| The type of the affinity that makes the request come to the same pod replica that was responding to the previous request. Set `session-affinity` to Cookie to enable session affinity. In the portal only, you must choose the enable session affinity box.|
25
+
|`session-max-age`|`session-cookie-max-age`| 0 |\[0, 604800\]| The time in seconds until the cookie expires, corresponding to the `Max-Age` cookie directive. If you set `session-max-age` to 0, the expiration period is equal to the browser session period.|
26
+
|`backend-protocol`|`backend-protocol`| Default | Default, `GRPC`| Sets the backend protocol to indicate how NGINX should communicate with the backend service. Default means HTTP/HTTPS/WebSocket. The `backend-protocol` setting only applies to client-to-app traffic. For app-to-app traffic within the same service instance, choose any protocol for app-to-app traffic without modifying the `backend-protocol` setting. The protocol doesn't restrict your choice of protocol for app-to-app traffic within the same service instance. |
27
+
|`client-auth`|`client-auth`| 0 selected | - | Select the certificates with the public key you uploaded in the TLS/SSL settings. Ingress concatenates these certificates into one and then uses it for client authentication.|
28
28
29
29
## Prerequisites
30
30
@@ -55,7 +55,7 @@ az spring app create \
55
55
```
56
56
57
57
> [!NOTE]
58
-
> the **cert-id**is in the format of `/subscriptions/<your-sub-id>/resourceGroups/<resource-group-name>/providers/Microsoft.AppPlatform/Spring/<service-name>/certificates/<cert-name>`, you can use the command `az spring certificate show -s <service-name> -g <resource-group-name> -n <cert-name> --query id` to get cert id.
58
+
> the `cert-id` value is in the format `/subscriptions/<your-sub-id>/resourceGroups/<resource-group-name>/providers/Microsoft.AppPlatform/Spring/<service-name>/certificates/<cert-name>`. To get the `cert-id` value, use the following command:`az spring certificate show --service <service-instance-name> --resource-group <resource-group-name> --name <certificate-name> --query id`
59
59
60
60
This command creates an app with the following settings:
61
61
@@ -121,7 +121,7 @@ This command updates the app with the following settings:
121
121
122
122
- What is the difference between ingress config and ingress settings?
123
123
124
-
Ingress config can still be used in the Azure CLI and SDK, and that setting applies to all apps within the service instance. Once ingress settings configured an app, the Ingress config can't affect it. We don't recommend that new scripts use ingress config since we plan to stop supporting it in the future.
124
+
Ingress config can still be used in the Azure CLI and SDK, and that setting applies to all apps within the service instance. After ingress settings configure an app, the Ingress config can't affect it. We don't recommend that new scripts use ingress config since we plan to stop supporting it in the future.
125
125
126
126
- When ingress settings are used together with App Gateway/APIM, what happens when you set the timeout in both Azure Spring Apps ingress and the App Gateway/APIM?
0 commit comments