MQTT Broker

The technical documentation of the mqtt-broker microservice, which forwards MQTT messages between the other microservices.

less than a minute

Kubernetes resources

StatefulSet: united-manufacturing-hub-hivemqce
Service:
- Internal ClusterIP:
  - HiveMQ local: united-manufacturing-hub-hivemq-local-service at port 1883 (MQTT) and 8883 (MQTT over TLS)
  - VerneMQ (for backwards compatibility): united-manufacturing-hub-vernemq at port 1883 (MQTT) and 8883 (MQTT over TLS)
  - VerneMQ local (for backwards compatibility): united-manufacturing-hub-vernemq-local-service at port 1883 (MQTT) and 8883 (MQTT over TLS)
- External LoadBalancer: united-manufacturing-hub-mqtt at port 1883 (MQTT) and 8883 (MQTT over TLS)
ConfigMap:
- Configuration: united-manufacturing-hub-hivemqce-hive
- Credentials: united-manufacturing-hub-hivemqce-extension
Secret: united-manufacturing-hub-hivemqce-secret-keystore
PersistentVolumeClaim:
- Data: united-manufacturing-hub-hivemqce-claim-data
- Extensions: united-manufacturing-hub-hivemqce-claim-extensions

Most of the configuration is done through the XML files in the ConfigMaps. The default configuration should be sufficient for most use cases.

The HiveMQ installation of the United Manufacturing Hub comes with these extensions:

RBAC file extension to manage the authentication and authorizations rules for the broker.
Prometheus extension to expose metrics for a prometheus applications
Heartbeat extension to allow for readiness checks

If you want to add more extensions, or to change the configuration, visit the HiveMQ documentation.

Environment variables
Variable name	Description	Type	Allowed values	Default
`HIVEMQ_ALLOW_ALL_CLIENTS`	Whether to allow all clients to connect to the broker	`bool`	`true`, `false`	`true`

Last modified January 22, 2024: Update version (074cc23)