Update chapter 4: Remove AMD references, update outputs to show 2 nodes/3 services, update to JSON response format

Author: geremyCohen

content/learning-paths/servers-and-cloud-computing/multiarch_nginx_on_aks/4-deploy-multiarch.md

@@ -8,11 +8,11 @@ layout: learningpathall
 
 ## Add multiarch service
 
-You now have nginx running on Intel, AMD, and ARM nodes with architecture-specific services. In this section, you'll create a multiarch service that can route to any available nginx pod regardless of architecture, providing load balancing across all architectures.
+You now have nginx running on Intel and ARM nodes with architecture-specific services. In this section, you'll create a multiarch service that can route to any available nginx pod regardless of architecture, providing load balancing across all architectures.
 
 ### Create the multiarch service
 
-The multiarch service targets all pods with the `app: nginx-multiarch` label (all nginx deployments share this label). It uses `sessionAffinity: None` to ensure requests are distributed across all available pods without stickiness, and can route to Intel, AMD, or ARM pods based on availability and load balancing algorithms.
+The multiarch service targets all pods with the `app: nginx-multiarch` label (all nginx deployments share this label). It uses `sessionAffinity: None` to ensure requests are distributed across all available pods without stickiness, and can route to Intel or ARM pods based on availability and load balancing algorithms.
 
 1. Run the following command to download and apply the multiarch service:
 
@@ -33,14 +33,13 @@ service/nginx-multiarch-svc created
 kubectl get svc -nnginx 
 ```
 
-Your output should be similar to the following, showing four services:
+Your output should be similar to the following, showing three services:
 
 ```output
-NAME                    TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE
-nginx-amd-svc           LoadBalancer   10.0.67.234    20.4.5.6        80:30081/TCP   25m
-nginx-arm-svc           LoadBalancer   10.0.89.145    20.7.8.9        80:30082/TCP   20m
-nginx-intel-svc         LoadBalancer   10.0.45.123    20.1.2.3        80:30080/TCP   45m
-nginx-multiarch-svc     LoadBalancer   10.0.123.456   20.10.11.12     80:30083/TCP   1m
+NAME                  TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)        AGE
+nginx-arm-svc         LoadBalancer   10.0.241.154   48.192.64.197   80:30082/TCP   7m52s
+nginx-intel-svc       LoadBalancer   10.0.226.250   20.80.128.191   80:30080/TCP   16m
+nginx-multiarch-svc   LoadBalancer   10.0.40.169    20.99.208.140   80:30083/TCP   38s
 ```
 
 3. Check which pods the multiarch service can route to:
@@ -49,11 +48,11 @@ nginx-multiarch-svc     LoadBalancer   10.0.123.456   20.10.11.12     80:30083/T
 kubectl get endpoints nginx-multiarch-svc -nnginx
 ```
 
-You should see all three architecture pods listed as endpoints:
+You should see both architecture pods listed as endpoints:
 
 ```output
-NAME                  ENDPOINTS                                      AGE
-nginx-multiarch-svc   10.244.0.217:80,10.244.1.177:80,10.244.2.68:80   1m
+NAME                  ENDPOINTS                      AGE
+nginx-multiarch-svc   10.244.0.21:80,10.244.1.1:80   47s
 ```
 
 ### Test the nginx multiarch service
@@ -67,9 +66,15 @@ nginx-multiarch-svc   10.244.0.217:80,10.244.1.177:80,10.244.2.68:80   1m
 You get back the HTTP response from one of the available pods:
 
 ```output
-Using service endpoint 20.10.11.12 for get on **multiarch service**
-Response: <title>Welcome to nginx!</title>
-Served by: nginx-**arm**-deployment-6f8d9c2a-def56
+Using service endpoint 20.99.208.140 for get on multiarch service
+Response:
+{
+  "message": "nginx response",
+  "timestamp": "2025-10-24T22:12:23+00:00",
+  "server": "nginx-arm-deployment-5bf8df95db-wznff",
+  "request_uri": "/"
+}
+Served by: nginx-arm-deployment-5bf8df95db-wznff
 ```
 
 5. Run the command multiple times to see load balancing across architectures:
@@ -80,14 +85,13 @@ Served by: nginx-**arm**-deployment-6f8d9c2a-def56
 ./nginx_util.sh get multiarch
 ```
 
-The pod logs will show requests being served by different architecture deployments (intel, amd, or arm), demonstrating that the multiarch service distributes load across all available pods.
+The responses will show requests being served by different architecture deployments (intel or arm), demonstrating that the multiarch service distributes load across all available pods.
 
 ### Compare architecture-specific vs multiarch routing
 
 Now you can compare the behavior:
 
 - **Architecture-specific**: `./nginx_util.sh get intel` always routes to Intel pods
-- **Architecture-specific**: `./nginx_util.sh get amd` always routes to AMD pods  
 - **Architecture-specific**: `./nginx_util.sh get arm` always routes to ARM pods
 - **Multiarch**: `./nginx_util.sh get multiarch` routes to any available pod