Merge pull request #736 from MicrosoftDocs/main

1/13/2025 PM Publish

Author: Taojunshen

articles/aks/TOC.yml

@@ -400,6 +400,14 @@
                   href: create-mongodb-infrastructure.md
                 - name: Deploy MongoDB cluster
                   href: deploy-mongodb-cluster.md
+                - name: Deploy Mongo Express client application
+                  href: validate-mongodb-cluster.md
+                - name: Test resiliency
+                  href: resiliency-mongodb-cluster.md
+                - name: Validate resiliency during node pool upgrade
+                  href: upgrade-mongodb-cluster.md
+                - name: Monitor with Percona Monitoring and Management
+                  href: monitor-aks-mongodb.md
             - name: Deploy a highly available PostgreSQL database
               items:
                 - name: Overview

articles/aks/configure-kubenet.md

@@ -226,7 +226,7 @@ When you create an AKS cluster, a network security group and route table are aut
 With kubenet, a route table must exist on your cluster subnet(s). AKS supports bringing your own existing subnet and route table. If your custom subnet doesn't contain a route table, AKS creates one for you and adds rules throughout the cluster lifecycle. If your custom subnet contains a route table when you create your cluster, AKS acknowledges the existing route table during cluster operations and adds/updates rules accordingly for cloud provider operations.
 
 > [!WARNING]
-> You can add/update custom rules on the custom route table. However, rules are added by the Kubernetes cloud provider which can't be updated or removed. Rules such as *0.0.0.0/0* must always exist on a given route table and map to the target of your internet gateway, such as an NVA or other egress gateway. Take caution when updating rules.
+> You can add/update custom rules on the custom route table. However, rules are added by the Kubernetes cloud provider which can't be updated or removed. Rules such as *0.0.0.0/0* generally exist on a given route table (unless the egress outbound type is `none`) and map to the target of your internet gateway, such as an NVA or other egress gateway. Take caution when updating rules.
 
 Learn more about setting up a [custom route table][custom-route-table].
 

articles/aks/create-mongodb-infrastructure.md

@@ -44,7 +44,7 @@ The following limitations apply when you create AKS clusters that support multip
 ## Create an AKS cluster
 
 > [!IMPORTANT]
-> If you run a single system node pool for your AKS cluster in a production environment, we recommend you use at least three nodes for the node pool. If one node goes down, you lose control plane resources and redundancy is compromised. You can mitigate this risk by having more control plane nodes.
+> If you run a single system node pool for your AKS cluster in a production environment, we recommend you use at least three nodes for the node pool. If one node goes down, the redundancy is compromised. You can mitigate this risk by having more system node pool nodes.
 
 1. Create an Azure resource group using the [`az group create`][az-group-create] command.
 

articles/aks/create-node-pools.md

@@ -5,7 +5,7 @@ author: nickomang
 ms.author: nickoman
 ms.subservice: aks-security
 ms.topic: how-to
-ms.date: 10/19/2023
+ms.date: 01/03/2025
 ms.custom: template-how-to, devx-track-azurecli
 ---
 
@@ -17,17 +17,16 @@ Follow the steps in [Use the Azure Key Vault provider for Secrets Store CSI Driv
 
 ### Enable and disable auto-rotation
 
-> [!NOTE]
-> When the Azure Key Vault provider for Secrets Store CSI Driver is enabled, it updates the pod mount and the Kubernetes secret defined in the `secretObjects` field of `SecretProviderClass`. It does so by polling for changes periodically, based on the rotation poll interval you defined. The default rotation poll interval is *two minutes*.
-
->[!NOTE]
-> When a secret updates in an external secrets store after initial pod deployment, the Kubernetes Secret and the pod mount periodically update depending on how the application consumes the secret data.
->
-> **Mount the Kubernetes Secret as a volume**: Use the auto-rotation and sync K8s secrets features of Secrets Store CSI Driver. The application needs to watch for changes from the mounted Kubernetes Secret volume. When the CSI Driver updates the Kubernetes Secret, the corresponding volume contents automatically update as well.
->
-> **Application reads the data from the container filesystem**: Use the rotation feature of Secrets Store CSI Driver. The application needs to watch for the file change from the volume mounted by the CSI driver.
->
-> **Use the Kubernetes Secret for an environment variable**: Restart the pod to get the latest secret as an environment variable. Use a tool such as [Reloader][reloader] to watch for changes on the synced Kubernetes Secret and perform rolling upgrades on pods.
+Once you enable auto-rotation for Azure Key Vault Secrets Provider, it updates the pod mount and the Kubernetes secret defined in the `secretObjects` field of `SecretProviderClass`. It does so by polling for changes periodically, based on the rotation poll interval you defined. The default rotation poll interval is *two minutes*.
+
+
+When a secret updates in an external secrets store after initial pod deployment, the Kubernetes Secret and the pod mount periodically update depending on how the application consumes the secret data.
+
+* Mount the Kubernetes Secret as a volume: Use the auto-rotation and sync K8s secrets features of Secrets Store CSI Driver. The application needs to watch for changes from the mounted Kubernetes Secret volume. When the CSI Driver updates the Kubernetes Secret, the corresponding volume contents automatically update as well.
+
+* Application reads the data from the container filesystem: Use the rotation feature of Secrets Store CSI Driver. The application needs to watch for the file change from the volume mounted by the CSI driver.
+
+* Use the Kubernetes Secret for an environment variable: Restart the pod to get the latest secret as an environment variable. Use a tool such as [Reloader][reloader] to watch for changes on the synced Kubernetes Secret and perform rolling upgrades on pods.
 
 #### Enable auto-rotation on a new AKS cluster