Shall we remove the loaded_modules in EMQX Enterprise 4.4.X ？

[Rory-Z]

Do we need to create the new APIVersion for v1beta4 and remove the loaded_modules field in EMQX Enterprise ?

For now，emqx-operator will create configmap for loaded_modules, and mount it in emqx container, but the problem is, when user update modules in EMQX Dashboard, EMQX will try write something for loaded_modules, and will got erofs error, because the loaded_modules file is read only.

The loaded_modules file is json file in EMQX Enterprise, initially I wanted the user to be able to modify it like a configuration file, but it is more complicated, users hardly ever modify it directly.

So, can we remove the loaded_modules in EMQX Enterprise 4.4.X, because it will cause erofs error in EMQX Running.

[Rory-Z]

Other idea, in v1beta3 APIVersion, if user didn't set modules, emqx operator will didn't create loaded_modules configMap anymore, if user set modules, emqx operator will create loaded_modules configMap like now

[ghost]

why not use a volume to storage all the moduler's configration files, so the emqx can get the configration modify auth.

[Rory-Z]

initially I wanted the user to be able to modify it like a configuration file

Users can not modify volume file like configuration