helm install emqx Custom EMQX_LOADED_PLUGINS about emqx-rel

[iMadriver]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

You can use kubectl logs to see if this is the same problem as mine

I checked the log and got [error] [Plugins] Write File "data/loaded_plugins" Error: erofs, seems the same as your issue

use version 4.2.13 for the time being
helm3 install test emqx/emqx -f values.yaml --version 4.2.13

wonderful!

[barisvelioglu]

Adding

EMQX_LOADED_PLUGINS: "emqx_dashboard"

gives me the same error. But when I try to load it by using

emqxLoadedPlugins: >

on values.yaml, it works fine

## EMQX configuration item, see the documentation (https://hub.docker.com/r/emqx/emqx)
emqxConfig:
  EMQX_NAME:  "{{ .Release.Name }}"

  ## Cluster discovery by dns
  # EMQX_CLUSTER__DISCOVERY: "dns"
  # EMQX_CLUSTER__DNS__NAME: "{{ .Release.Name }}-headless.{{ .Release.Namespace }}.svc.cluster.local"
  # EMQX_CLUSTER__DNS__APP: "{{ .Release.Name }}"
  # EMQX_CLUSTER__DNS__TYPE: "srv"

  ## Cluster discovery by k8s
  EMQX_CLUSTER__DISCOVERY: "k8s"
  EMQX_CLUSTER__K8S__APP_NAME: "{{ .Release.Name }}"
  EMQX_CLUSTER__K8S__APISERVER: "https://kubernetes.default.svc:443"
  EMQX_CLUSTER__K8S__SERVICE_NAME: "{{ .Release.Name }}-headless"
  EMQX_CLUSTER__K8S__NAMESPACE: "{{ .Release.Namespace }}"
  ## The address type is used to extract host from k8s service.
  ## Value: ip | dns | hostname
  ## Note：Hostname is only supported after v4.0-rc.2
  EMQX_CLUSTER__K8S__ADDRESS_TYPE: "hostname"
  EMQX_CLUSTER__K8S__SUFFIX: "svc.cluster.local"
  EMQX_ALLOW_ANONYMOUS: false
  EMQX_AUTH__MONGO__SERVER: "mongodb:27017"
  EMQX_AUTH__MONGO__LOGIN: "root"
  EMQX_AUTH__MONGO__PASSWORD: "mycrazystrongpublicpassword"
  EMQX_AUTH__MONGO__AUTH_SOURCE: "admin"
  EMQX_AUTH__MONGO__AUTH_QUERY__PASSWORD_HASH: "sha256"
  ## if EMQX_CLUSTER__K8S__ADDRESS_TYPE eq dns
  # EMQX_CLUSTER__K8S__SUFFIX: "pod.cluster.local"

## --------------------------------------------------------------------
##  [ACL](https://docs.emqx.io/broker/latest/en/advanced/acl-file.html)

##  -type(who() :: all | binary() |
##                 {ipaddr, esockd_access:cidr()} |
##                 {client, binary()} |
##                 {user, binary()}).

##  -type(access() :: subscribe | publish | pubsub).

##  -type(topic() :: binary()).

##  -type(rule() :: {allow, all} |
##                  {allow, who(), access(), list(topic())} |
##                  {deny, all} |
##                  {deny, who(), access(), list(topic())}).
## --------------------------------------------------------------------
emqxAclConfig: >
  {allow, {user, "dashboard"}, subscribe, ["$SYS/#"]}.
  {allow, {ipaddr, "127.0.0.1"}, pubsub, ["$SYS/#", "#"]}.
  {deny, all, subscribe, ["$SYS/#", {eq, "#"}]}.
  {allow, all}.

emqxLoadedPlugins: >
  {emqx_management, true}.
  {emqx_recon, true}.
  {emqx_retainer, true}.
  {emqx_dashboard, true}.
  {emqx_telemetry, true}.
  {emqx_rule_engine, true}.
  {emqx_bridge_mqtt, false}.
  {emqx_auth_mongo, true}.

emqxLoadedModules: >
  {emqx_mod_acl_internal, true}.
  {emqx_mod_presence, true}.
  {emqx_mod_trace, false}.
  {emqx_mod_st_statistics, false}.
  {emqx_mod_delayed, true}.
  {emqx_mod_rewrite, true}.
  {emqx_mod_subscription, true}.
  {emqx_mod_topic_metrics, true}.

[liuxingjun]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

I use 4.2.13 temporarily available

[lpaulusLohr]

Update, I have same issue with 4.3.8 need to rollback to 4.2.13

[iMadriver]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

[liuxingjun]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

You can use kubectl logs to see if this is the same problem as mine

[iMadriver]

My emqx/emqx version is 4.3.5. And after I added EMQX_LOADED_PLUGINS: "emqx_auth_mnesia" in values.yaml, it seems ok but nothing changes. The emqx_auth_mnesia is still not started, verifired in dashboard.

[iMadriver]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

You can use kubectl logs to see if this is the same problem as mine

I checked the log and got [error] [Plugins] Write File "data/loaded_plugins" Error: erofs, seems the same as your issue

[liuxingjun]

Hi， did you solved your issue? I hope to start "emqx_auth_mnesia" with helm commands, and result in "CrashLoopBackOff".

You can use kubectl logs to see if this is the same problem as mine

I checked the log and got [error] [Plugins] Write File "data/loaded_plugins" Error: erofs, seems the same as your issue

use version 4.2.13 for the time being
helm3 install test emqx/emqx -f values.yaml --version 4.2.13

[gcdd1993]

mark, I have same issue with 4.3.11

[barisvelioglu]

Same issue as well with 4.4.0

[ylcrow]

kubectl edit configmap xxxx--loaded-plugins

[xiemeilong]

Same issue as well with 4.4.2

[zhonghuali]

Same issue as well with latest version 4.4.19, but docker run work fine.

[Rory-Z]

Hi guys, now EMQ X no longer uses this repository since version 4.3. Use https://github.com/emqx/emqx/ instead.