articles-about-ingress-for-aks

Author: ShawnJackson

articles/application-gateway/ingress-controller-autoscale-pods.md

@@ -14,7 +14,7 @@ ms.author: greglin
 
 As incoming traffic increases, it becomes crucial to scale up your applications based on the demand.
 
-This article explains how you can use the `AvgRequestCountPerHealthyHost` metric in Azure Application Gateway to scale up an application. The `AvgRequestCountPerHealthyHost` metric measures average requests sent to a specific combination of a back-end pool and a back-end HTTP setting.
+This article explains how you can use the `AvgRequestCountPerHealthyHost` metric in Azure Application Gateway to scale up Azure Kubernetes Service (AKS) pods for an application. The `AvgRequestCountPerHealthyHost` metric measures average requests sent to a specific combination of a back-end pool and a back-end HTTP setting.
 
 Use the following two components:
 

articles/application-gateway/ingress-controller-expose-service-over-http-https.md

@@ -23,11 +23,11 @@ This article illustrates the usage of [Kubernetes ingress resources](https://kub
 
 ## Deploy the guestbook application
 
-The guestbook application is a canonical Kubernetes application that consists of a Web UI front end, a back end, and a Redis database.
+The `guestbook` application is a canonical Kubernetes application that consists of a Web UI front end, a back end, and a Redis database.
 
 By default, `guestbook` exposes its application through a service with the name `frontend` on port `80`. Without a Kubernetes ingress resource, the service isn't accessible from outside the AKS cluster. You use the application, and set up ingress resources to access the application, through HTTP and HTTPS.
 
-To deploy the guestbook application:
+To deploy the `guestbook` application:
 
 1. Download `guestbook-all-in-one.yaml` from [this GitHub page](https://raw.githubusercontent.com/kubernetes/examples/master/guestbook/all-in-one/guestbook-all-in-one.yaml).
 1. Deploy `guestbook-all-in-one.yaml` into your AKS cluster by running this command:
@@ -38,7 +38,7 @@ To deploy the guestbook application:
 
 ## Expose services over HTTP
 
-To expose the guestbook application, use the following ingress resource:
+To expose the `guestbook` application, use the following ingress resource:
 
 ```yaml
 apiVersion: networking.k8s.io/v1
@@ -74,7 +74,7 @@ Now the `guestbook` application should be available. You can check the availabil
 
 ### Without a specified host name
 
-If you don't specify a host name, the guestbook service is available on all the host names that point to the Application Gateway instance.
+If you don't specify a host name, the `guestbook` service is available on all the host names that point to the Application Gateway instance.
 
 1. Before you deploy the ingress resource, create a Kubernetes secret to host the certificate and private key:
 
@@ -116,7 +116,7 @@ Now the `guestbook` application is available on both HTTP and HTTPS.
 
 ### With a specified host name
 
-You can also specify the host name on the ingress resource in order to multiplex TLS configurations and services. When you specify a host name, the guestbook service is available only on the specified host.
+You can also specify the host name on the ingress resource in order to multiplex TLS configurations and services. When you specify a host name, the `guestbook` service is available only on the specified host.
 
 1. Define the following ingress resource. In the `secretName` section, replace `<guestbook-secret-name>` with the name of your secret. In the `hosts` and `host` sections, replace `<guestbook.contoso.com>` with your host name.
 

articles/application-gateway/ingress-controller-install-existing.md

@@ -10,7 +10,7 @@ ms.date: 9/17/2024
 ms.author: greglin
 ---
 
-# Install an Application Gateway Ingress Controller (AGIC) by using an existing Application Gateway instance
+# Install AGIC by using an existing Application Gateway instance
 
 The Application Gateway Ingress Controller (AGIC) is a pod within your Azure Kubernetes Service (AKS) cluster. AGIC monitors the Kubernetes [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) resources. It creates and applies an Azure Application Gateway configuration based on the status of the Kubernetes cluster.
 

articles/application-gateway/ingress-controller-install-new.md

@@ -10,7 +10,7 @@ ms.date: 9/17/2024
 ms.author: greglin
 ---
 
-# Install an Application Gateway Ingress Controller (AGIC) by using a new Application Gateway instance
+# Install AGIC by using a new Application Gateway instance
 
 The instructions in this article assume that you want to install an Application Gateway Ingress Controller (AGIC) in an environment that has no preexisting components.
 

articles/application-gateway/ingress-controller-multiple-namespace-support.md

@@ -9,15 +9,15 @@ ms.date: 08/01/2023
 ms.author: greglin
 ---
 
-# Enable multiple-namespace support in an AKS cluster by using the Application Gateway Kubernetes Ingress Controller
+# Enable multiple-namespace support in an AKS cluster by using AGIC
 
 [Kubernetes namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) make it possible for a Kubernetes cluster to be partitioned and allocated to subgroups of a larger team. These subgroups can then deploy and manage infrastructure with finer controls of resources, security, and configuration. Kubernetes allows for one or more ingress resources to be defined independently within each namespace.
 
 As of version 0.7, the [Application Gateway Kubernetes Ingress Controller](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/README.md) (AGIC) can ingest events from and observe multiple namespaces. If an Azure Kubernetes Service (AKS) administrator decides to use [Azure Application Gateway](https://azure.microsoft.com/services/application-gateway/) as an ingress, all namespaces use the same instance of Application Gateway. A single installation of AGIC monitors accessible namespaces and configures the Application Gateway instance that it's associated with.
 
 Version 0.7 of AGIC continues to exclusively observe the `default` namespace, unless you explicitly change it to one or more different namespaces in the Helm configuration.
 
-## Enable support for multiple namespaces
+## Enable multiple-namespace support
 
 1. Modify the [helm-config.yaml](#sample-helm-configuration-file) file in one of the following ways:
 

articles/application-gateway/ingress-controller-update-ingress-controller.md

@@ -10,7 +10,7 @@ ms.date: 07/23/2023
 ms.author: greglin
 ---
 
-# Upgrade the Application Gateway Ingress Controller by using Helm
+# Upgrade AGIC by using Helm
 
 You can upgrade the Azure Application Gateway Ingress Controller (AGIC) for Kubernetes by using a Helm repository hosted on Azure Storage.