Merge pull request #183515 from zr-msft/zr-aks-rollback-ingress-change

[AKS] roll back changes to ingress article

Author: PRMerger14

articles/aks/ingress-basic.md

@@ -32,25 +32,9 @@ This article also requires that you are running the Azure CLI version 2.0.64 or
 
 In addition, this article assumes you have an existing AKS cluster with an integrated ACR. For more details on creating an AKS cluster with an integrated ACR, see [Authenticate with Azure Container Registry from Azure Kubernetes Service][aks-integrated-acr].
 
-## Basic configuration
-To create a simple NGINX ingress controller without customizing the defaults, you will use helm.
+## Import the images used by the Helm chart into your ACR
 
-```console
-NAMESPACE=ingress-basic
-
-helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
-helm repo update
-
-helm install ingress-nginx ingress-nginx/ingress-nginx --create-namespace --namespace $NAMESPACE 
-```
-
-Note that the above configuration uses the 'out of the box' configuration for simplicity.  If needed, you could add parameters for customizing the deployment, eg, `--set controller.replicaCount=3`.  The next section will show a highly customized example of the ingress controller.
-
-## Customized configuration
-As an alternative to the basic configuration presented in the above section, the next set of steps will show how to deploy a customized ingress controller.
-### Import the images used by the Helm chart into your ACR
-
-To control image versions, you will want to import them into your own Azure Container registry.  The [NGINX ingress controller Helm chart][ingress-nginx-helm-chart] relies on three container images. Use `az acr import` to import those images into your ACR.
+This article uses the [NGINX ingress controller Helm chart][ingress-nginx-helm-chart], which relies on three container images. Use `az acr import` to import those images into your ACR.
 
 ```azurecli
 REGISTRY_NAME=<REGISTRY_NAME>
@@ -70,7 +54,7 @@ az acr import --name $REGISTRY_NAME --source $SOURCE_REGISTRY/$DEFAULTBACKEND_IM
 > [!NOTE]
 > In addition to importing container images into your ACR, you can also import Helm charts into your ACR. For more information, see [Push and pull Helm charts to an Azure container registry][acr-helm].
 
-### Create an ingress controller
+## Create an ingress controller
 
 To create the ingress controller, use Helm to install *nginx-ingress*. For added redundancy, two replicas of the NGINX ingress controllers are deployed with the `--set controller.replicaCount` parameter. To fully benefit from running replicas of the ingress controller, make sure there's more than one node in your AKS cluster.
 
@@ -109,8 +93,6 @@ helm install nginx-ingress ingress-nginx/ingress-nginx \
     --set defaultBackend.image.digest=""
 ```
 
-## Check the load balancer service
-
 When the Kubernetes load balancer service is created for the NGINX ingress controller, a dynamic public IP address is assigned, as shown in the following example output:
 
 ```