Release Note 🍻
EMQX Operator 1.2.4 is released.
Warning 🚨
Only supported 4.4.6 and later versions of EMQX and EMQX Enterprise
Features 🌈
-
Users can add extra Containers to the pod, see #252.
-
When deploy EMQX Custom Resource, if exist PVCs, set
.spec.podManagementPolicy = "Parallel"
, or else, set.spec.podManagementPolicy = "OrderedReady"
, this can avoid to some extent the problem of EMQX cluster brain cleavage. -
Add
username
andpassword
to.spec.emqxTemplate
for EMQX Custom Resource, users can use them to set up the dashboard and API authentication, and also, users will no longer be able to create and modifyemqx_management
andemqx_dashboard
plugins by EMQX Plugin Custom Resource. -
If users didn't set
acl
in.spec.emqxTemplate
, the ConfigMap will not be created. -
For EMQX Enterprise, if users didn't set
modules
in.spec.emqxTemplate
, the ConfigMap will not be created. -
New fields for
.status
in EMQX Custom Resource. -
Now we don't create
volume
andvolumeMount
for EMQX logs anymore, EMQX logs will output to container stdout by default.
What's Changed
- feat: get the listeners port by API after the emqx cluster is ready by @Rory-Z in #308
- chore: delete default probe by @Rory-Z in #313
- chore: add default value for username and password by @Rory-Z in #314
- update emqx modules by @Rory-Z in #307
- chore: dump emqx version to 4.4.6 by @Rory-Z in #316
- chore: format annotations for statefulSet by @Rory-Z in #315
- chore: pre relase 1.2.4 by @Rory-Z in #317
- chore: add failed reconciled to emqx status by @Rory-Z in #318
- ci: update upgrade check by @Rory-Z in #319
- ci: use latest condition to check emqx status by @Rory-Z in #321
Full Changelog: 1.2.3...1.2.4