fix: Fix recommended minimum node count for system node pools of AKS (#747)

Co-authored-by: Kyle Poineal <38540295+kpoineal@users.noreply.github.com>

Author: tksh164

azure-resources/ContainerService/managedClusters/kql/7f7ae535-a5ba-4665-b7e0-c451dbdda01f.kql

@@ -5,6 +5,6 @@ resources
 | mv-expand agentPoolProfile = properties.agentPoolProfiles
 | extend taints = tostring(parse_json(agentPoolProfile.nodeTaints))
 | extend nodePool = tostring(parse_json(agentPoolProfile.name))
-| where taints has "CriticalAddonsOnly=true:NoSchedule" and  agentPoolProfile.minCount < 2
+| where taints has "CriticalAddonsOnly=true:NoSchedule" and  agentPoolProfile.minCount < 3
 | project recommendationId="7f7ae535-a5ba-4665-b7e0-c451dbdda01f", name, id, tags, param1=strcat("nodePoolName: ", nodePool), param2=strcat("nodePoolMinNodeCount: ", agentPoolProfile.minCount)
 

azure-resources/ContainerService/managedClusters/recommendations.yaml

@@ -295,7 +295,7 @@
   recommendationResourceType: Microsoft.ContainerService/managedClusters
   recommendationMetadataState: Active
   longDescription: |
-    The system node pool should be configured with a minimum node count of two to ensure critical system pods are resilient to node outages.
+    The system node pool should be configured with a minimum node count of three to ensure critical system pods are resilient to node outages.
   potentialBenefits: Ensures pod resilience
   pgVerified: true
   automationAvailable: true