Enhancements

• #10022 Release installation packages for Rocky Linux 9 (compatible with Red Hat Enterprise Linux 9) and macOS 12 for Intel platform.

• #10139 Add extraVolumeMounts to EMQX Helm Chart, you can mount user's own files to EMQX instance, such as ACL rule files mentioned in #9052.

• #9893 When connecting with the flag clean_start=false, EMQX will filter out messages that published by clients banned by the blacklist feature in the session. Previously, messages sent by clients banned by the blacklist feature could still be delivered to subscribers in this case.

• #9986 Add MQTT ingress to helm charts and remove obsolete mgmt references.

• #9564 Implement Kafka Consumer Bridge, which supports consuming messages from Kafka and publishing them to MQTT topics.

• #9881 Improve error logging related to health checks for InfluxDB connections.

• #9985 Implement ClickHouse Data Bridge.

• #10123 Improve the performance of /bridges API. Earlier, when the number of nodes in the cluster was large or the node was busy, the API may had a request timeout.

• #9998 Obfuscate request body in error log when using HTTP service for client authentication for security reasons.

• #10026 Metrics are now only exposed via the /bridges/:id/metrics endpoint, and no longer returned in other API operations.

• #10052 Improve startup failure logs in daemon mode.

Bug Fixes

• #10013 Fix return type structure for error case in API schema for /gateways/:name/clients.

• #10014 Ensure Monitor API /monitor(_current)/nodes/:node returns 404 instead of 400 if node does not exist.

• #10027 Allow setting node name via environment variable EMQX_NODE__NAME in Docker.

• #10050 Ensure Bridge API returns 404 status code consistently for resources that don't exist.

• #10055 The configuration parameter mqtt.max_awaiting_rel was not functional and has now been corrected.

• #10056 Fix /bridges API status code. Return 400 instead of 403 in case of removing a data bridge that is dependent on an active rule. Return 400 instead of 403 in case of calling operations (start|stop|restart) when Data-Bridging is not enabled.

• #10066 Improve error messages for /briges_probe and [/node/:node]/bridges/:id/:operation API calls to make them more readable. And set HTTP status code to 400 instead of 500.

• #10074 Check if type in PUT /authorization/sources/:type matches type given in the request body.

• #10079 Fix wrong description about shared_subscription_strategy.

• #10085 Consistently return 404 for all requests on non-existent source in /authorization/sources/:source[/*].

• #10095 Fix an issue where when the MySQL connector was in batch mode, clients would keep querying the server with unnecessary PREPARE statements on each batch, possibly causing server resource exhaustion.

• #10098 Fix an issue where the MongoDB connector crashed when MongoDB authorization was configured.

• #10100 Fix channel crash for slow clients with enhanced authentication.
  Previously, when the client was using enhanced authentication, but the Auth message was sent slowly or the Auth message was lost, the client process would crash.

• #10107 For operations on Bridges API if bridge-id is unknown we now return 404 instead of 400.

• #10117 Fix an error occurring when a joining node doesn't have plugins that are installed on other nodes in the cluster. After this fix, the joining node will copy all the necessary plugins from other nodes.

• #10118 Fix problems related to manual joining of EMQX replicant nodes to the cluster.

• #10119 Fix crash when statsd.server is set to an empty string.

• #10124 The default heartbeat period for MongoDB has been increased to reduce the risk of too excessive logging to the MongoDB log file.

• #10130 Fix garbled config display in dashboard when the value is originally from environment variables.

• #10132 Fix some error logs generated by systemctl stop emqx command.
  Prior to the fix, the command was not stopping jq and os_mon applications properly.

• #10144 Fix an issue where emqx cli failed to set the Erlang cookie when the emqx directory was read-only.

• #10154 Change the default resume_interval for bridges and connectors to be the minimum of health_check_interval and request_timeout / 3 to resolve issue of request timeout.

• #10157 Fix default rate limit configuration not being applied correctly when creating a new listener.

• #10202 Fix the issue where nodes responses to the list bridges RPC were incorrectly flattened, which caused List Bridges API HTTP handler to crash when there was more than 1 node in the cluster

• #10237 Ensure we return 404 status code for unknown node names in /nodes/:node[/metrics|/stats] API.

• #10251 Fix an issue where rule dependencies were not prompted when deleting an ingress-type bridge in use.

• #10269 Fix an issue when TDEngine connection would not start when the password is empty. Fixed by making password a required field for this data bridge.

• #10313 Ensure that when the core or replicant node starting, the cluster-override.conf file is only copied from the core node.

• #10327 Don't increase “actions.failed.unknown” rule metrics counter upon receiving unrecoverable data bridge errors.