Merge pull request #114035 from mscatyao/caya-appgw-updates

AppGW Updates

Author: PRMerger14

articles/application-gateway/configuration-overview.md

@@ -96,18 +96,18 @@ For this scenario, use NSGs on the Application Gateway subnet. Put the following
 
    You can create a UDR to send 0.0.0.0/0 traffic directly to the Internet. 
 
-  **Scenario 3**: UDR for Azure Kubernetes Service kubenet
+  **Scenario 3**: UDR for Azure Kubernetes Service with kubenet
 
-  If you're using kubenet with Azure Kubernetes Service (AKS) and Application Gateway Ingress Controller (AGIC), you need to set up a route table to allow traffic sent to the pods to be routed to the correct node. This won't be necessary if you use Azure CNI. 
+  If you're using kubenet with Azure Kubernetes Service (AKS) and Application Gateway Ingress Controller (AGIC), you'll need a route table to allow traffic sent to the pods from Application Gateway to be routed to the correct node. This won't be necessary if you use Azure CNI. 
 
-   To set up the route table to allow kubenet to work, use the following steps:
+  To use the route table to allow kubenet to work, follow the steps below:
 
-  1. Create a Route Table resource in Azure. 
-  2. Once it's created, go to the **Routes** page. 
-  3. Add a new route:
+  1. Go to the resource group created by AKS (the name of the resource group should begin with "MC_")
+  2. Find the route table created by AKS in that resource group. The route table should be populated with the following information:
      - Address prefix should be the IP range of the pods you want to reach in AKS. 
-     - Next hop type should be **Virtual Appliance**. 
-     - Next hop address should be the IP address of the node hosting the pods within the IP range defined in the address prefix field. 
+     - Next hop type should be Virtual Appliance. 
+     - Next hop address should be the IP address of the node hosting the pods.
+  3. Associate this route table to the Application Gateway subnet. 
 
   **v2 unsupported scenarios**
 

articles/application-gateway/ssl-overview.md

@@ -24,6 +24,10 @@ Application Gateway supports TLS termination at the gateway, after which traffic
 
 To configure TLS termination, a TLS/SSL certificate is required to be added to the listener to enable the application gateway to derive a symmetric key as per TLS/SSL protocol specification. The symmetric key is then used to encrypt and decrypt the traffic sent to the gateway. The TLS/SSL certificate needs to be in Personal Information Exchange (PFX) format. This file format allows you to export the private key that is required by the application gateway to perform the encryption and decryption of traffic.
 
+> [!IMPORTANT] 
+> Please note that the certificate on the listener requires the entire certificate chain to be uploaded. 
+
+
 > [!NOTE] 
 >
 > Application gateway does not provide any capability to create a new certificate or send a certificate request to a certification authority.