Update trust bundle name

Author: jlian

articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md

@@ -420,7 +420,7 @@ spec:
           expirationSeconds: 86400
   - name: trust-bundle
     configMap:
-      name: aio-ca-trust-bundle-test-only # Default root CA cert
+      name: azure-iot-operations-aio-ca-trust-bundle # Default root CA cert
 ```
 
 Apply the deployment file with kubectl.

articles/iot-operations/create-edge-apps/howto-develop-dapr-apps.md

@@ -113,7 +113,7 @@ The following definition components might require customization to your specific
           # Certificate chain for Dapr to validate the MQTT broker
           - name: aio-ca-trust-bundle
             configMap:
-              name: aio-ca-trust-bundle-test-only
+              name: azure-iot-operations-aio-ca-trust-bundle
 
           containers:
           # Container for the Dapr application 

articles/iot-operations/create-edge-apps/howto-develop-mqttnet-apps.md

@@ -100,7 +100,7 @@ spec:
   # Certificate chain for the application to validate the MQTT broker              
   - name: aio-ca-trust-bundle
     configMap:
-      name: aio-ca-trust-bundle-test-only
+      name: azure-iot-operations-aio-ca-trust-bundle
 
   containers:
   - name: mqtt-client-dotnet

articles/iot-operations/create-edge-apps/tutorial-event-driven-with-dapr.md

@@ -91,7 +91,7 @@ To start, create a yaml file that uses the following definitions:
           # Certificate chain for Dapr to validate the MQTT broker
           - name: aio-ca-trust-bundle
             configMap:
-              name: aio-ca-trust-bundle-test-only
+              name: azure-iot-operations-aio-ca-trust-bundle
 
           containers:
           - name: mq-event-driven-dapr
@@ -189,7 +189,7 @@ To verify the MQTT bridge is working, deploy an MQTT client to the cluster.
               expirationSeconds: 86400
       - name: aio-ca-trust-bundle
         configMap:
-          name: aio-ca-trust-bundle-test-only
+          name: azure-iot-operations-aio-ca-trust-bundle
     ```
 
 1. Apply the deployment file with kubectl:

articles/iot-operations/manage-mqtt-broker/howto-test-connection.md

@@ -41,14 +41,20 @@ The first option is to connect from within the cluster. This option uses the def
 
     ```yaml
     apiVersion: v1
+    kind: ServiceAccount
+    metadata:
+      name: mqtt-client
+      namespace: azure-iot-operations
+    ---
+    apiVersion: v1
     kind: Pod
     metadata:
       name: mqtt-client
       # Namespace must match MQTT broker BrokerListener's namespace
       # Otherwise use the long hostname: aio-broker.azure-iot-operations.svc.cluster.local
       namespace: azure-iot-operations
     spec:
-      # Use the "mqtt-client" service account which comes with default deployment
+      # Use the "mqtt-client" service account created from above
       # Otherwise create it with `kubectl create serviceaccount mqtt-client -n azure-iot-operations`
       serviceAccountName: mqtt-client
       containers:
@@ -128,10 +134,10 @@ The first option is to connect from within the cluster. This option uses the def
 
 Since the broker uses TLS, the client must trust the broker's TLS certificate chain. You need to configure the client to trust the root CA certificate used by the broker.
 
-To use the default root CA certificate, download it from the `aio-ca-trust-bundle-test-only` ConfigMap:
+To use the default root CA certificate, download it from the `azure-iot-operations-aio-ca-trust-bundle` ConfigMap:
 
 ```bash
-kubectl get configmap aio-ca-trust-bundle-test-only -n azure-iot-operations -o jsonpath='{.data.ca\.crt}' > ca.crt
+kubectl get configmap azure-iot-operations-aio-ca-trust-bundle -n azure-iot-operations -o jsonpath='{.data.ca\.crt}' > ca.crt
 ```
 
 Use the downloaded `ca.crt` file to configure your client to trust the broker's TLS certificate chain.