You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md
+9-45Lines changed: 9 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -512,58 +512,22 @@ When you publish to the `tutorial/local` topic on the local Azure IoT Operations
512
512
513
513
## Deploy MQTT client
514
514
515
-
To verify the MQTT bridge is working, deploy an MQTT client to the same namespace as Azure IoT Operations. In a new file named `client.yaml`, specify the client deployment:
516
-
517
-
<!-- TODO: put this in the explore-iot-operations repo? -->
515
+
To verify the MQTT bridge is working, deploy an MQTT client to the same namespace as Azure IoT Operations.
518
516
519
517
# [Bicep](#tab/bicep)
520
518
521
-
Currently, bicep doesn't apply to deploy MQTT client.
519
+
Currently, Bicep doesn't apply to deploy MQTT client.
522
520
523
521
# [Kubernetes (preview)](#tab/kubernetes)
524
522
525
-
```yaml
526
-
apiVersion: v1
527
-
kind: ServiceAccount
528
-
metadata:
529
-
name: mqtt-client
530
-
namespace: azure-iot-operations
531
-
---
532
-
apiVersion: v1
533
-
kind: Pod
534
-
metadata:
535
-
name: mqtt-client
536
-
# Namespace must match MQTT broker BrokerListener's namespace
537
-
# Otherwise use the long hostname: aio-broker.azure-iot-operations.svc.cluster.local
538
-
namespace: azure-iot-operations
539
-
spec:
540
-
# Use the "mqtt-client" service account from above
541
-
# Otherwise create it with `kubectl create serviceaccount mqtt-client -n azure-iot-operations`
0 commit comments