Skip to content

Commit be5e2c4

Browse files
committed
Remove mqttui
1 parent c1a0c90 commit be5e2c4

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

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

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -119,15 +119,6 @@ The first option is to connect from within the cluster. This option uses the def
119119

120120
The mosquitto client uses the same service account token and root CA cert to authenticate with the broker and subscribe to the topic.
121121

122-
1. You can also use mqttui to connect to the broker using the service account token. The `--insecure` flag is required because mqttui doesn't support TLS certificate chain verification with a custom root CA cert.
123-
124-
> [!CAUTION]
125-
> Using `--insecure` is not recommended for production scenarios. Only use it for testing or development purposes.
126-
127-
```console
128-
mqttui --broker mqtts://aio-mq-dmqtt-frontend:8883 --insecure -D CONNECT authentication-method 'K8S-SAT' -D CONNECT authentication-data $(cat /var/run/secrets/tokens/mq-sat)
129-
```
130-
131122
1. To remove the pod, run `kubectl delete pod mqtt-client -n azure-iot-operations`.
132123

133124
## Connect clients from outside the cluster to default the TLS port

0 commit comments

Comments
 (0)