fix(container): update image public.ecr.aws/emqx/emqx to v5.8.9#373
Open
renovate[bot] wants to merge 1 commit into
Open
fix(container): update image public.ecr.aws/emqx/emqx to v5.8.9#373renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
--- kubernetes/apps/database/emqx/cluster Kustomization: flux-system/emqx-cluster EMQX: database/emqx
+++ kubernetes/apps/database/emqx/cluster Kustomization: flux-system/emqx-cluster EMQX: database/emqx
@@ -52,13 +52,13 @@
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 200Mi
storageClassName: openebs-hostpath
- image: public.ecr.aws/emqx/emqx:5.8.5
+ image: public.ecr.aws/emqx/emqx:5.8.9
listenersServiceTemplate:
metadata:
annotations:
lbipam.cilium.io/ips: 192.168.20.135
spec:
type: LoadBalancer |
98bc557 to
7192363
Compare
7192363 to
666113c
Compare
666113c to
5d25d14
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.8.5→5.8.9Release Notes
emqx/emqx (public.ecr.aws/emqx/emqx)
v5.8.9: EMQX v5.8.9Compare Source
Enhancements
#16491 Start releasing packages for macOS 15 (Sequoia)
#15911 Now, for the HTTP Action, the HTTP request timeout is taken to be the same as
resource_opts.request_ttl. Previously, it was a fixed, non-configurable value of 30 seconds.#15845 Extended the
static_clientidsconfiguration of MQTT Connector to allow specifying usernames and passwords associated with each clientid.Bug Fixes
Core MQTT Functionalities
#16349 Fixed a crash in MQTT v5 connections caused by a type mismatch when processing the request-response-information property.
#16081 Fixed an issue where, if a client used extended authentication mechanisms and memory sessions, they could crash with an
session_stepdown_request_exceptionerror andcalling_selfreason.e.g.:
#15872 Eliminate warning log
unclean_terminatewhen disconnected after CONNACK is sent with a non-zero reason code.#15902 Upgraded MQTT client library to 1.13.8
This improves MQTT bridge connectivity with:
#15884 Resolved an issue where, in rare cases, the global routing table could indefinitely retain routing information for nodes that had long since left the cluster.
This also fixes a race condition that could cause accumulating inconsistencies in the routing table and shared subscription state when a large number of shared subscribers disconnect simultaneously.
Clustering
#16452 Upgraded
gen_rpcto3.5.1.Prior to the
gen_rpcupgrade, EMQX may experience long tail of crash logs due to connect timeout if a peer node is unreachable.The new version
gen_rpcno longer has the long tail and converted crash logs to more readableerrorlogs,and the frequent log
"failed_to_connect_server"is also throttled to avoid spamming.Security and Authentication
#15844 Added validation to forbid adding empty usernames to the built-in database authenticator. Such users cannot be deleted via the HTTP API later, since they mess up the API path.
If you have such an user and wish to delete it, run the following in an EMQX console:
#15818 Corrected handling of
{allow|deny, all}ACL rules.Previously, these rules were internally translated to match
#, which incorrectly failed to match topics prefixed with$(e.g.$testtopic/1) due to MQTT spec restrictions.Now, a special internal value is used to ensure
{allow|deny, all}rules correctly match any topic, including$-prefixed ones.#15899 Improved memory usage: authorization (authz) cache is now cleared immediately when a client disconnects, reducing unnecessary memory consumption.
Rule Engine
#16028 Fixed rule engine
jqfunction memory leak.Previously if
jqbuilt-in functionindexis used (e.g..key | index("name")), it would result in memory leak.Durable Storage
Breaking Changes
v5.8.8: EMQX v5.8.8Compare Source
Enhancements
Deployment
Core MQTT Functionalities
137(Server Busy) in theCONNACKwith Reason-String"THROTTLED", and should retry after the cleanup completes.137instead of133.Observability
Performance
node.global_gc_intervalconfiguration by default to improve overall performance stability, as it caused CPU fluctuations and higher message latency while providing little benefit over Erlang’s built-in garbage collector.+zdbbl 32768) to preventbusy_dist_port alarmsduring intensive Mnesia operations.+sbwt none +sbwtdcpu none +sbwtdio none) to lower CPU usage reported by the operating system.+stbt db) to reduce message latency.Bug Fixes
Deployment
#15580 Added a new
emqxLicenseSecretRefvariable to the EMQX Enterprise Helm chart. This allows users to specify a Kubernetes Secret containing the EMQX license key, so the license is applied automatically.This replaces the non-functional
emqxLicenseSecretNamevariable, which created and mounted a secret file but did not pass the license to EMQX.Clustering
data/certsordata/authzdirectories.Security
bad_certificate/invalid_signature error.Observability
packets.subscribe.auth_errormetric was not incremented when subscription authentication failed.Gateway
unknown:global, causing conflicts between gateways.ExHook
v5.8.7: EMQX v5.8.7Compare Source
Bug Fixes
v5.8.6: EMQX v5.8.6Compare Source
Enhancement
#14869 Added the
connected_attimestamp field to the$events/client_disconnectedevent payload. This enhancement enables tracking the original connection session time for disconnected clients, preventing outdated disconnect events from overriding newer connection states.Previously, when clients frequently reconnected due to unstable networks, delayed disconnect events could lead to incorrect session tracking. With this update, the
connected_atfield is now included in the event payload, aligning its behavior with system topics and ensuring accurate session state management.Bug Fixes
Core MQTT Functionalities
Installation and Deployment
#14797 Fixed macOS release package startup issue due to OpenSSL dynamic linking (backport #14624).
Previously, the EMQX ZIP package on macOS could fail to start because the
quicerapplication dynamically linked to the system-installed OpenSSL, which was not signed during the EMQX build process. Now we have disabled dynamic linking for OpenSSL, aligning with the OTP shipped on macOS. This ensures EMQX starts reliably on macOS 13 and later.Authentication
REST API
Content-Typeheader when downloading data backup files. Previously, the response header for downloaded backup files incorrectly usedapplication/jsoninstead ofapplication/octet-stream.Rule Engine
detailskey in alarm events. Previously, when testingalarm_activatedoralarm_deactivatedevents in the SQL Rule Tester, certain values in thedetailskey could cause an HTTP 500 error due to improper handling of nested map keys.Observability
#14800 Throttled
warninglevel logdropped_qos0_msg.#14793 Added trace log for
protocol_errorin MQTT connections.Previously, when a client sent invalid or unexpected MQTT packets causing a
protocol_error, EMQX logs provided limited details, making it difficult to diagnose the issue.For example, if a client sent a second
CONNECTpacket while already connected, EMQX would logsocket_force_closedwithprotocol_error, but without indicating the exact cause.With this update, EMQX now logs
unexpected_connect_packetwithconn_state=connectedbeforesocket_force_closed, providing clearer context for debugging protocol violations.Plugin
#14802 Introduced a new CLI command for plugins:
Breaking Changes
#14802 Starting from this version, plugin installation via the REST API or Dashboard requires explicit permission. Users must obtain this permission using the following CLI command before installing.
This change enhances security by preventing unauthorized plugin installations. Users managing plugins via the API or Dashboard must adjust their workflows accordingly.
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.