Added update from PM

Author: flang-msft

articles/azure-cache-for-redis/cache-tutorial-active-replication.md

@@ -19,6 +19,8 @@ In this tutorial, you will host a simple inventory application on Azure Kubernet
 
 - An Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - Two Azure Kubernetes Service Clusters in different regions- For more information on creating a cluster, see [Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal](/azure/aks/learn/quick-kubernetes-deploy-portal). Alternatively, you can host two instances of the demo application on the same AKS cluster.
+<!-- SP -->
+- One Azure Kubernetes Service Cluster - For more information on creating a cluster, see [Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal](/azure/aks/learn/quick-kubernetes-deploy-portal). Alternately, you can host two instances of the demo application on the two different AKS clusters, which will how your production environment will be set up. However, for this tutorial, we will deploy both instances of the application on the same AKS cluster.
 
 > [!IMPORTANT]
 > This tutorial assumes that you are familiar with basic Kubernetes concepts like containers, pods and service.
@@ -52,6 +54,8 @@ To demonstrate data replication across regions, we run two instances of the same
 
     1. Update environment variables `REDIS_HOST` and `REDIS_PASSWORD` with _hostname_ and _access key_ of your _West US 2_ cache.
     1. Update `APP_LOCATION` to display the region where this application instance is running. For this cache, configure the `APP_LOCATION` to _Seattle_ to indicate this application instance is running in Seattle.
+    <!-- sp -->
+    1. Update environment variables REDIS_HOST and REDIS_PASSWORD with endpoint (remove the suffix ":10000") and access key of your Azure Cache for Redis Enterprise instance in West US 2 or one of the two regions your chose earlier.
 
     ```YAML
     apiVersion: apps/v1
@@ -81,7 +85,7 @@ To demonstrate data replication across regions, we run two instances of the same
                 memory: "128Mi"
             env:
              - name: REDIS_HOST
-               value: "DemoWest.westus.redisenterprise.cache.azure.net"
+               value: "DemoWest.westus2.redisenterprise.cache.azure.net"
              - name: REDIS_PASSWORD
                value: "myaccesskey"
              - name: REDIS_PORT
@@ -108,8 +112,65 @@ To demonstrate data replication across regions, we run two instances of the same
 
 1. Save another copy of the same YAML file as _app_east.yaml_. This time, use different values.
 
-   1. Update environment variables `REDIS_HOST` and `REDIS_PASSWORD` with _hostname_ and _access key_ of your _East US_ cache.
+   1. Update environment variables `REDIS_HOST` and `REDIS_PASSWORD` with Eendpoint_ and _access key_ of your _East US_ cache.
    1. Update `APP_LOCATION` to display the region where this application instance is running. For this cache, configure the `APP_LOCATION` to _New York_ to indicate this application instance is running in New York.
+   
+   1. +Save another copy of the same YAML file as app_east.yaml. This time, update the namespace, REDIS_HOST, REDIS_PASSWORD and APP_LOCATION to point to Redis Enterprise instance in East US or your second region of choice.
+
+It should look like below: 
+
+```YAML
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: shoppingcart-app
+  namespace: east
+spec:
+  replicas: 1 
+  selector:
+    matchLabels:
+      app: shoppingcart
+  template:
+    metadata:
+      labels:
+        app: shoppingcart
+    spec:
+      containers:
+      - name: demoapp
+        image: mcr.microsoft.com/azure-redis-cache/redisactivereplicationdemo:latest
+        resources:
+          limits:
+            cpu: "0.5"
+            memory: "250Mi"
+          requests:
+            cpu: "0.5"
+            memory: "128Mi"
+        env:
+         - name: REDIS_HOST
+           value: "DemoEast.eastus.redisenterprise.cache.azure.net"
+         - name: REDIS_PASSWORD
+           value: "myaccesskey"
+         - name: REDIS_PORT
+           value: "10000"   # redis enterprise port
+         - name: HTTP_PORT
+           value: "8080"
+         - name: APP_LOCATION
+           value: "New York, NY" 
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: shoppingcart-svc
+  namespace: east
+spec:
+  type: LoadBalancer
+  ports:
+  - protocol: TCP
+    port: 80
+    targetPort: 8080
+  selector:
+    app: shoppingcart
+```
 
 ## Install and connect to your AKS cluster
 
@@ -130,13 +191,12 @@ If you use Azure Cloud Shell, _kubectl_ is already installed, and you can skip t
 Use the portal to copy the resource group and cluster name for your AKS cluster in the West US 2 region. To configure _kubectl_ to connect to your AKS cluster, use the following command with your resource group and cluster name:
 
 ```bash
- az aks get-credentials --resource-group myResourceGroup --name myClusterName -f AKS_WestUS2
+ az aks get-credentials --resource-group myResourceGroup --name myClusterName
  ```
 
 Verify that you are able to connect to your cluster by running the following command:
 
 ```bash
-set kubeconfig=AKS_WestUS2
 
 kubectl get nodes
 ```
@@ -150,26 +210,15 @@ aks-agentpool-21274953-vmss000003   Ready    agent   1d    v1.24.15
 aks-agentpool-21274953-vmss000006   Ready    agent   1d    v1.24.15
 ```
 
-Now, repeat the steps for getting credentials for your AKS cluster in East US region.
-
-```bash
-az aks get-credentials --resource-group myResourceGroup --name myClusterName -f AKS_EastUS
-
-set kubeconfig=AKS_EastUS
-
-kubectl get nodes
-```
-
-Thus, you now have context on your machine to connect to both the AKS clusters on your machine. 
-Alternately, you can apply the YAML files to appropriate AKS clusters through portal directly. To apply YAML through portal, go to the "Services and ingresses" blade for your AKS cluster, and click on the "Create" and choose "Apply a YAML" option. This will open an editor where you can copy paste your YAML file.
-
 
 ## Deploy and test your application
 
-Run the following command to deploy the application instance to your AKS cluster in **West US 2**:
+You need two namespaces for your applications to run on your AKS cluster. Create a west and then deploy the application.
+
+Run the following command to deploy the application instance to your AKS cluster in the _west_ namespace:
 
 ```bash
-set kubeconfig=AKS_WestUS2
+kubectl create namespace west
 
 kubectl apply -f app_west.yaml
 ```
@@ -209,14 +258,14 @@ shoppingcart-svc       LoadBalancer   10.0.166.147   20.69.136.105   80:30390/TC
 
 Once the External-IP is available, open a web browser to the External-IP address of your service and you see the application running like below:
 
-<!-- <screenshot for Seattle> -->
+<!-- screenshot for Seattle -->
 
 Run the same deployment steps and deploy an instance of the demo application to run in East US region.
 
 ```bash
-set kubeconfig=AKS_EastUS
+kubectl create namespace east
 
-kubectl apply -f app_east
+kubectl apply -f app_east.yml
 
 kubectl get pods -n east