Merge pull request #260599 from EthanChangAED/main

Update kubectl commands

Author: prmerger-automator[bot]

articles/iot-operations/manage-layered-network/howto-configure-l4-cluster-layered-network.md

@@ -186,7 +186,7 @@ Once your Kubernetes cluster is Arc-enabled, you can deploy the Layered Network
 1. Use the *kubectl* command to verify the Layered Network Management operator is running.
 
     ```bash
-    kubectl get pods
+    kubectl get pods -n azure-iot-operations
     ```
 
     ```output
@@ -272,7 +272,7 @@ Create the Layered Network Management custom resource.
 1. View the Layered Network Management Kubernetes service:
 
     ```bash
-    kubectl get services
+    kubectl get services -n azure-iot-operations
     ```
 
     ```output

articles/iot-operations/manage-layered-network/howto-configure-layered-network.md

@@ -94,7 +94,7 @@ While the DNS setup can be achieved many different ways, this example uses an ex
 After the level 4 cluster and Layered Network Management are ready, perform the following steps.
 1. Confirm the IP address of Layered Network Management service with the following command:
     ```bash
-    kubectl get services
+    kubectl get services -n azure-iot-operations
     ```
     The output should look like the following. The IP address of the service is `20.81.111.118`.
 
@@ -106,7 +106,7 @@ After the level 4 cluster and Layered Network Management are ready, perform the
 1. View the config maps with following command:
 
     ```bash
-    kubectl get cm
+    kubectl get cm -n azure-iot-operations
     ```
 
     The output should look like the following example:
@@ -124,7 +124,7 @@ After the level 4 cluster and Layered Network Management are ready, perform the
       export PARENT_IP_ADDR="20.81.111.118"
     
     # run the script to generate a config map yaml
-      kubectl get cm aio-lnm-level4-client-config -o yaml | yq eval '.metadata = {"name": "coredns-custom", "namespace": "kube-system"}' -| sed 's/PARENT_IP/'"$PARENT_IP_ADDR"'/' > configmap-custom-level4.yaml
+      kubectl get cm aio-lnm-level4-client-config -n azure-iot-operations -o yaml | yq eval '.metadata = {"name": "coredns-custom", "namespace": "kube-system"}' -| sed 's/PARENT_IP/'"$PARENT_IP_ADDR"'/' > configmap-custom-level4.yaml
     ```
 
     This step creates a file named `configmap-custom-level4.yaml`

articles/iot-operations/manage-layered-network/howto-deploy-aks-layered-network.md

@@ -48,7 +48,7 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
 1. To validate the installation was successful, run:
 
     ```bash
-    kubectl get pods
+    kubectl get pods -n azure-iot-operations
     ```
 
     You should see an output that looks like the following example:
@@ -131,7 +131,7 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
 1. To validate the instance, run:
 
     ```bash
-    kubectl get pods
+    kubectl get pods -n azure-iot-operations
     ```
 
     The output should look like:
@@ -145,7 +145,7 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
 1. To view the service, run:
 
     ```bash
-    kubectl get services
+    kubectl get services -n azure-iot-operations
     ```
 
     The output should look like the following example:
@@ -157,7 +157,7 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
 1. To view the config maps, run:
 
     ```bash
-    kubectl get cm
+    kubectl get cm -n azure-iot-operations
     ```
     The output should look like the following example:
     ```