Staging net-new content for Jerry's review

ryanberg-aquent · ryanberg-aquent · commit c0f5e128e8c9 · 2025-09-03T08:14:52.000-10:00
diff --git a/support/azure/azure-kubernetes/load-bal-ingress-c/troubleshoot-performance-ingress.md b/support/azure/azure-kubernetes/load-bal-ingress-c/troubleshoot-performance-ingress.md
@@ -5,28 +5,28 @@ ms.reviewer: claudiogodoy
 ms.service: azure-kubernetes-service
 ms.date: 05/24/2025
 ---
-# Managed NGINX Ingress Controller Troubleshoot
+# Managed NGINX ingress controller guidance
 
-The [Managed NGINX ingress controller](/azure/aks/app-routing) is a routing add-on that enables routing Hypertext Transfer Protocol (HTTP) and secure (HTTPS) traffic to applications running on an [Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/) cluster.
+The [Managed NGINX ingress controller](/azure/aks/app-routing) is a routing add-on that enables routing HTTP and HTTPS traffic to applications running on an [Azure Kubernetes Service (AKS)](/azure/aks/) cluster.
 
 In performance-related problems, the routing system may be the root cause. This article provides step-by-step guidance to troubleshoot NGINX ingress controller performance issues.
 
 ## Prerequisites
 
-Before you start, ensure you have the following tools installed:
+Before you start, ensure you have the following tool installed:
 
-- **Kubernetes CLI (`kubectl`)**: Use Azure CLI to install it by running the command `az aks install-cli`.
+- **Kubernetes CLI (`kubectl`)**: Use Azure CLI and run the command `az aks install-cli`.
 
-## Common Symptoms
+## Symptoms
 
 | Symptom | Description |
 | --- | --- |
-| **HTTP Gateway Errors** | Error codes such as 502, 504 might indicate an NGINX exhaustion problem. |
-| **High Response Time Difference** | Significant difference between your service response time and the end-to-end response time. There's a common latency added by NGINX, but when it's too large, you might have an NGINX exhaustion problem. |
+| **HTTP Gateway Errors** | Error codes like `502` and `504` can indicate an NGINX exhaustion problem. |
+| **High Response Time Difference** | Significant difference between your service response time and the end-to-end response time. There's a common latency added by NGINX. When it's too large, you might have an NGINX exhaustion problem. |
 
-## Step 1: Verify HPA Behavior
+## Step 1: Verify horizontal pod autoscaler (HPA) behavior
 
-The most common reason for performance issues on the NGINX is CPU exhaustion. During a load spike in the system, a good approach is to watch the [HPA](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) behavior.
+The most common reason for performance issues on the NGINX is CPU exhaustion. During a load spike in the system, a good approach is to monitor [HPA](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) behavior.
 By default, the routing add-on creates a [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) named `app-routing-system`.
 
 1. **Get the HPA name**:
@@ -35,13 +35,13 @@ By default, the routing add-on creates a [namespace](https://kubernetes.io/docs/
     kubectl get hpa -n app-routing-system
     ```
 
-2. **Watch the HPA behavior**:
+2. **Monitor the HPA behavior**:
 
     ```console
     kubectl get hpa <HPA_NAME> -n app-routing-system -w
     ```
 
-3. **Evaluate the result**:
+3. **Evaluate the results**:
 
     ```console
     $ kubectl get hpa <HPA_NAME> -n app-routing-system -w
@@ -52,35 +52,35 @@ By default, the routing add-on creates a [namespace](https://kubernetes.io/docs/
     nginx   Deployment/nginx   cpu: 133%/70%        1         2         2          80m
     ```
 
-The **TARGETS** column shows the CPU threshold where the `HPA` will trigger to scale up the pods. You must interpret this behavior. There are a few possibilities:
+The **TARGETS** column shows the CPU threshold where the `HPA` triggers to scale up the pods. There are a few possibilities for this behavior:
 
-- The `HPA` has reached the maximum number of pods.
+- `HPA` has reached the maximum number of pods.
 - There are no available nodes to schedule the pods.
 
-## Step 2: Look for Pods in Pending State
+## Step 2: Look for pods in pending state
 
-If in the previous step you saw that the `NGINX HPA` hasn't reached the maximum number of pods, the [kube-scheduler](https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/#kube-scheduler) might be struggling to find available nodes to schedule the `NGINX pods`.
+If in your evaluation you saw that `NGINX HPA` hadn't reached the maximum number of pods, the [kube-scheduler](https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/#kube-scheduler) might not be able to find available nodes to schedule the `NGINX pods`.
 
-1. **Get Pending Pods**:
+1. **Get pending pods**:
 
     ```console
     kubectl get pod --field-selector=status.phase=Pending -n app-routing-system
     ```
 
  > [!NOTE]
-> If there are Pending pods, the cluster is probably facing a resource exhaustion problem. In this case, refer to [Troubleshoot pod scheduler errors in Azure Kubernetes Service](azure/azure-kubernetes/availability-performance/troubleshoot-pod-scheduler-errors).
+> If there are pending pods, the cluster is probably facing a resource exhaustion problem. See [Troubleshoot pod scheduler errors in Azure Kubernetes Service](azure/azure-kubernetes/availability-performance/troubleshoot-pod-scheduler-errors) for more details.
 
-## Step 3: Verify if There Are Limits Applied to the NGINX Deployment
+## Step 3: Verify if there are Limits applied to the NGINX deployment
 
-Any misconfiguration on the `NGINX` [resource limits or requests](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) might lead to `HPA` scaling up more pods than necessary.
+Any misconfiguration on the `NGINX` [resource limits or requests](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) can lead to `HPA` scaling up more pods than necessary.
 
-1. **Describe the NGINX Deployment**:
+1. **Describe the NGINX deployment**:
 
     ```console
     kubectl describe deploy nginx -n app-routing-system
     ```
 
-2. **Verify Requests and Limits**:
+2. **Verify requests and limits**:
 
     ```console
     $ kubectl describe deploy nginx -n app-routing-system
@@ -101,11 +101,11 @@ Any misconfiguration on the `NGINX` [resource limits or requests](https://kubern
 
 ## Solution
 
-By default, the current version of the NGINX ingress controller does not set limits for NGINX pods and requests `500m` CPU, which is used by the `HPA`. It is not recommended to change these values directly in the deployment definition.
+By default, the current version of the NGINX ingress controller doesn't set limits for NGINX pods and requests `500m` CPU, which is used by the `HPA`. It's not recommended to change these values directly in the deployment definition.
 
-If your `HPA` is reaching the maximum number of pods and the deployment's requests and limits remain unchanged, you should configure the [custom resource definition (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) called [NginxIngressController](https://github.com/Azure/aks-app-routing-operator/blob/main/config/crd/bases/approuting.kubernetes.azure.com_nginxingresscontrollers.yaml).
+If your `HPA` is reaching the maximum number of pods and the deployment's requests and limits remain unchanged, configure the [custom resource definition (CRD)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) named [NginxIngressController](https://github.com/Azure/aks-app-routing-operator/blob/main/config/crd/bases/approuting.kubernetes.azure.com_nginxingresscontrollers.yaml).
 
-### Configuration Options
+### Configuration options
 
 The following configuration options directly impact the `HPA` behavior:
 
@@ -114,11 +114,9 @@ The following configuration options directly impact the `HPA` behavior:
 | `scaling`      | object  | Configuration for scaling the controller. Contains nested properties.       | No       | -         |
 | `maxReplicas`  | integer | Upper limit for replicas.                                                  | No       | 100       |
 | `minReplicas`  | integer | Lower limit for replicas.                                                  | No       | 2         |
-| `threshold`    | string  | Scaling threshold defining how aggressively to scale. Options: `rapid`, `steady`, `balanced`. | No       | balanced  |
+| `threshold`    | string  | Scaling threshold defining how aggressively to scale. Options include: `rapid`, `steady`, `balanced`. | No       | balanced  |
 
-### How to Apply the Configuration
-
-Follow these steps to apply the configuration:
+### Apply the configuration
 
 1. **Edit the NginxIngressController CRD**:
 
@@ -144,7 +142,7 @@ Follow these steps to apply the configuration:
     kubectl get hpa -n app-routing-system
     ```
 
-The HPA will automatically update based on your new configuration, and the NGINX ingress controller will scale according to the specified parameters.
+The HPA automatically updates based on your new configuration and the NGINX ingress controller scales according to the specified parameters.
 
 ## Additional resources
 
diff --git a/support/azure/azure-kubernetes/toc.yml b/support/azure/azure-kubernetes/toc.yml
@@ -153,7 +153,7 @@
   - name: Troubleshoot Application Gateway Ingress Controller connectivity
     href: load-bal-ingress-c/troubleshoot-app-gateway-ingress-controller-connectivity-issues.md
   - name: Troubleshoot Performance Issues with the Managed NGINX Ingress Controller in AKS
-    href: load-bal-ingress-c/tshoot-performance-ingress.md
+    href: load-bal-ingress-c/troubleshoot-performance-ingress.md
 
 - name: Troubleshoot Kubernetes control plane
   items:
