Merge pull request #269381 from MicrosoftDocs/main

3/18/2024 PM Publish

articles/advisor/index.yml

@@ -46,5 +46,5 @@ landingContent:
           - text: PowerShell
             url: /powershell/module/az.advisor/
           - text: REST API
-            url: /rest/api/advisor/
+            url: /rest/api/advisor/operation-groups
 

articles/advisor/toc.yml

@@ -44,6 +44,8 @@
   items:
   - name: Use Azure Well Architected Framework Assessments
     href: advisor-assessments.md
+  - name: Use Azure Advisor resiliency reviews
+    href: advisor-resiliency-reviews.md
   - name: Optimize virtual machine spend by resizing or shutting down underutilized instances
     href: advisor-cost-recommendations.md
   - name: Optimize your Azure costs using the cost optimization workbook 

articles/ai-services/openai/includes/fine-tuning-rest.md

@@ -247,7 +247,7 @@ The only limitations are that the new region must also support fine-tuning and w
 Below is an example of deploying a model that was fine-tuned in one subscription/region to another.
 
 ```bash
-curl -X POST "https://management.azure.com/subscriptions/<SUBSCRIPTION>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.CognitiveServices/accounts/<RESOURCE_NAME>/deployments/<MODEL_DEPLOYMENT_NAME>api-version=2023-05-01" \
+curl -X PUT "https://management.azure.com/subscriptions/<SUBSCRIPTION>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.CognitiveServices/accounts/<RESOURCE_NAME>/deployments/<MODEL_DEPLOYMENT_NAME>api-version=2023-05-01" \
   -H "Authorization: Bearer <TOKEN>" \
   -H "Content-Type: application/json" \
   -d '{

articles/aks/TOC.yml

@@ -288,8 +288,6 @@
               href: artifact-streaming.md
             - name: Add an Azure Spot node pool
               href: spot-node-pool.md
-            - name: Multi-instance GPU node pool
-              href: gpu-multi-instance.md
             - name: Node pool snapshot
               href: node-pool-snapshot.md
             - name: Use system node pools
@@ -305,7 +303,31 @@
             - name: Use the Azure portal
               href: virtual-nodes-portal.md
     - name: Workloads
-      items:
+      items:    
+        - name: GPU workloads
+          items:
+            - name: Use GPUs
+              href: gpu-cluster.md
+            - name: Use Windows GPUs
+              href: use-windows-gpu.md
+            - name: Multi-instance GPU node pool
+              href: gpu-multi-instance.md
+        - name: Vertical Pod Autoscaler
+          items:
+            - name: About Vertical Pod Autoscaler 
+              href: vertical-pod-autoscaler.md
+            - name: Vertical Pod Autoscaler API reference
+              href: vertical-pod-autoscaler-api-reference.md
+        - name: Configure Metrics Server VPA
+          href: use-metrics-server-vertical-pod-autoscaler.md
+        - name: Proximity placement groups
+          href: reduce-latency-ppg.md
+        - name: Cluster autoscaler
+          items:
+            - name: Cluster autoscaler overview
+              href: cluster-autoscaler-overview.md
+            - name: Use the cluster autoscaler on AKS
+              href: cluster-autoscaler.md
         - name: Node autoprovision
           href: node-autoprovision.md
         - name: Availability zones
@@ -452,6 +474,8 @@
               href: azure-cni-overlay.md
             - name: Use Azure CNI for dynamic IP allocation
               href: configure-azure-cni-dynamic-ip-allocation.md
+            - name: Use Azure CNI VNet - Static Block Allocation (Preview)
+              href: configure-azure-cni-static-block-allocation.md
             - name: Use Azure CNI Powered by Cilium
               href: azure-cni-powered-by-cilium.md
             - name: Use kubenet
@@ -744,8 +768,6 @@
           href: /visualstudio/bridge/bridge-to-kubernetes-vs?toc=/azure/aks/toc.json&bc=/azure/aks/breadcrumb/toc.json
         - name: Use OpenFaaS
           href: openfaas.md
-        - name: Use GPUs
-          href: gpu-cluster.md
         - name: Create containerized app with Draft
           href: draft.md
         - name: Build Django app with PostgreSQL

articles/aks/azure-cni-overview.md

@@ -6,7 +6,7 @@ ms.author: allensu
 ms.service: azure-kubernetes-service
 ms.subservice: aks-networking
 ms.topic: concept-article
-ms.date: 9/13/2023
+ms.date: 02/29/2024
 
 #CustomerIntent: As a network administrator, I want learn about Azure CNI networking so that I can deploy Azure CNI networking in an AKS cluster.
 ---
@@ -19,7 +19,7 @@ With [Azure Container Networking Interface (CNI)][cni-networking], every pod get
 
 > [!NOTE]
 > 
-> This article is only introducing traditional Azure CNI. For [Azure CNI Overlay][azure-cni-overlay] and [Azure CNI for dynamic IP allocation][configure-azure-cni-dynamic-ip-allocation], refer to their documentation instead.  
+> This article is only introducing traditional Azure CNI. For [Azure CNI Overlay][azure-cni-overlay], [Azure CNI VNet for dynamic IP allocation][configure-azure-cni-dynamic-ip-allocation], and [Azure CNI VNet - Static Block Allocation (Preview)][configure-azure-cni-static-block-allocation]. Please refer to their documentation instead.  
 
 ## Prerequisites
 
@@ -193,3 +193,4 @@ Learn more about networking in AKS in the following articles:
 [prerequisites]: configure-azure-cni.md#prerequisites
 [azure-cni-overlay]: azure-cni-overlay.md
 [configure-azure-cni-dynamic-ip-allocation]: configure-azure-cni-dynamic-ip-allocation.md
+[configure-azure-cni-static-block-allocation]: configure-azure-cni-static-block-allocation.md

articles/aks/concepts-scale.md

@@ -2,7 +2,7 @@
 title: Concepts - Scale applications in Azure Kubernetes Services (AKS)
 description: Learn about scaling in Azure Kubernetes Service (AKS), including the horizontal pod autoscaler, cluster autoscaler, and Azure Container Instances.
 ms.topic: conceptual
-ms.date: 01/22/2024
+ms.date: 03/18/2024
 ---
 
 # Scaling options for applications in Azure Kubernetes Service (AKS)
@@ -59,6 +59,14 @@ The cluster autoscaler also monitors the pod scheduling status for nodes that ha
 
 Your applications may experience some disruption as pods are scheduled on different nodes when the cluster autoscaler decreases the number of nodes. To minimize disruption, avoid applications that use a single pod instance.
 
+## Kubernetes Event-driven Autoscaling (KEDA)
+
+[Kubernetes Event-driven Autoscaling][keda-official-documentation] (KEDA) is an open source component for event-driven autoscaling of workloads. It scales workloads dynamically based on the number of events received. KEDA extends Kubernetes with a custom resource definition (CRD), referred to as a *ScaledObject*, to describe how applications should be scaled in response to specific traffic.
+
+KEDA scaling is useful in scenarios where workloads receive bursts of traffic or handle high volumes of data. It is different from Horizontal Pod Autoscaler, as KEDA is event-driven and scales based on the number of events, while HPA is metrics-driven based on the resource utilization (for example, CPU and memory).
+
+To get started with the KEDA add-on in AKS, see [KEDA overview][keda-overview].
+
 ## Burst to Azure Container Instances (ACI)
 
 To rapidly scale your AKS cluster, you can integrate with Azure Container Instances (ACI). Kubernetes has built-in components to scale the replica and node count. However, if your application needs to rapidly scale, the [horizontal pod autoscaler](#horizontal-pod-autoscaler) may schedule more pods than can be provided by the existing compute resources in the node pool. If configured, this scenario would then trigger the [cluster autoscaler](#cluster-autoscaler) to deploy more nodes in the node pool, but it may take a few minutes for those nodes to successfully provision and allow the Kubernetes scheduler to run pods on them.
@@ -78,6 +86,7 @@ To get started with scaling applications, see the following resources:
 - Manually scale [pods][kubectl-scale-reference] or [nodes][aks-manually-scale-nodes]
 - Use the [horizontal pod autoscaler][aks-hpa]
 - Use the [cluster autoscaler][aks-cluster-autoscaler]
+- Use the [Kubernetes Event-driven Autoscaling (KEDA) add-on][keda-addon]
 
 For more information on core Kubernetes and AKS concepts, see the following articles:
 
@@ -90,6 +99,7 @@ For more information on core Kubernetes and AKS concepts, see the following arti
 <!-- LINKS - external -->
 [virtual-kubelet]: https://virtual-kubelet.io/
 [kubectl-scale-reference]: https://kubernetes.io/docs/reference/kubectl/generated/kubectl_scale/
+[keda-official-documentation]: https://keda.sh/docs/2.13/concepts/
 
 <!-- LINKS - internal -->
 [aks-hpa]: tutorial-kubernetes-scale.md#autoscale-pods
@@ -101,4 +111,5 @@ For more information on core Kubernetes and AKS concepts, see the following arti
 [aks-concepts-storage]: concepts-storage.md
 [aks-concepts-identity]: concepts-identity.md
 [aks-concepts-network]: concepts-network.md
-[virtual-nodes-cli]: virtual-nodes-cli.md
+[virtual-nodes-cli]: virtual-nodes-cli.md
+[keda-overview]: keda-about.md

articles/aks/concepts-security.md

@@ -4,7 +4,7 @@ description: Learn about security in Azure Kubernetes Service (AKS), including m
 author: miwithro
 ms.topic: conceptual
 ms.custom: build-2023
-ms.date: 01/11/2024
+ms.date: 03/18/2024
 ms.author: miwithro
 ---
 
@@ -56,6 +56,8 @@ When an AKS cluster is created or scaled up, the nodes are automatically deploye
 
 For more information about the security upgrade process for Linux and Windows worker nodes, see [Security patching nodes][aks-vulnerability-management-nodes].
 
+AKS clusters running Azure Generation 2 VMs includes support for [Trusted Launch][trusted-launch] (preview), which protects against advanced and persistent attack techniques by combining technologies that can be independently enabled, like secure boot and virtualized version of trusted platform module (vTPM). Administrators can deploy AKS worker nodes with verified and signed bootloaders, OS kernels, and drivers to ensure integrity of the entire boot chain of the underlying VM.
+
 ### Node authorization
 
 Node authorization is a special-purpose authorization mode that specifically authorizes kubelet API requests to protect against East-West attacks.  Node authorization is enabled by default on AKS 1.24 + clusters.
@@ -160,3 +162,4 @@ For more information on core Kubernetes and AKS concepts, see:
 [microsoft-vulnerability-management-aks]: concepts-vulnerability-management.md
 [aks-vulnerability-management-nodes]: concepts-vulnerability-management.md#worker-nodes
 [manage-ssh-access]: manage-ssh-node-access.md
+[trusted-launch]: use-trusted-launch.md