Replies: 4 comments 1 reply
-
|
The plugin works. Thanks to this information I was able to get it working. However, the modules are still broken. https://github.com/emqx/emqx-operator/blob/main/config/samples/emqx/v1beta3/emqx-plugin.yaml |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @xtianus79 Looks like some problems with EMQX, I already ping EMQX developer to check that, thx |
Beta Was this translation helpful? Give feedback.
-
|
Hi @id Looks emqx/emqx#8977 is closed, anything update ? |
Beta Was this translation helpful? Give feedback.
-
|
@Rory-Z added to roadmap for v5.0.24. Unless something urgent takes priority, we'll look into it in the next 2-3 weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Cool, if have any update, please let me know. |
Beta Was this translation helpful? Give feedback.
-
From the looks of it and the countless days and documentation readings it seems as if the pods in my AKS subnet cannot be configured without breaking the broker.
No plugins or modules work when setting the URL.
I have a deployed service over 443 that can be clearly reached inside of the emqx pod(s) via curl but setting the conf such as redis or such as emqx_auth_http.conf will absolutely not work when changing the url to a service inside of the subnet or over the internet via 80 or 443.
What am I missing. It doesn't make any sense to me.
i've posted an issue here.
emqx/emqx#8977
But more of a broader question. Where is the documentation and what could I possibly be missing that this is not working?
I would think that my services could exist via in the subnet and or via 443/80.
Beta Was this translation helpful? Give feedback.
All reactions