Add ingress settings doc

Author: CaihuaRui

articles/spring-apps/how-to-configure-ingress.md

@@ -21,9 +21,9 @@ The Azure Spring Apps service uses an underlying ingress controller to handle ap
 |----------------------|------------------------|---------------|-------------------|--------------------------------------------------------------------------|
 | ingress-read-timeout | proxy-read-timeout     | 300           | \[1,1800\]        | The timeout in seconds for reading a response from a proxied server.     |
 | ingress-send-timeout | proxy-send-timeout     | 60            | \[1,1800\]        | The timeout in seconds for transmitting a request to the proxied server. |
-| session-affinity     | affinity               | None          | \[Session, None\] | Type of the affinity, set this to Cookie to enable session affinity.     |
+| session-affinity     | affinity               | None          | Session, None     | Type of the affinity, which will make the request come to the same pod replica that was responding to the request before. Set this to Cookie to enable session affinity, in the portal only need to choose the enable session affinity box.    |
 | session-max-age      | session-cookie-max-age | 0             | \[0,7 days\]      | Time seconds until the cookie expires, corresponds to the Max-Age cookie directive. If set to 0, the expiration period is equal to the browser session period. |
-| 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 setting is only about client-to-app traffic, for app-to-app traffic within the same service instance, you can use any protoco. |
+| 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 setting is only about client-to-app traffic, for app-to-app traffic within the same service instance, you may choose any protocol for app-to-app traffic without modifying this option, that is the protocol here does not restrict your choice of protocol for app-to-app traffic within the same service instance.  |
 
 ## Prerequisites
 
@@ -95,8 +95,7 @@ This command will update the ingress read timeout to 600 seconds, ingress send t
   - For WebSocket connection limit, the upper limit is 20000, and when you reach that limit the connection will fail.
   - You can use RSocket based on WebSocket, as well as you set the backend protocol to `Default`.
 
-- Can I still use the old ingress config settings?
-  - Yes, you can still use old ingress config in sdk, but once an app has been configured by new ingress settings, the old ingress config will not affect it.
+- The `ingress config` still can be used in CLI and sdk, and that setting will apply to all apps within the service instance, but once an app has been configured by `ingress settings`, the `ingress config` will not affect it. We do not recommend new scripts to use "ingress config" any more, since we plan to stop supporting it in the future.
 
 - When ingress settings are used together with App Gateway/APIM, what is the overall effect of timeout when you set the timeout in both ASA ingress and the App Gateway/APIM?
   - The shorter timeout should be effective.