When the replicas is 1, I can access to dashboard normally.
But when I scale replicas to 2 or 3, it had the message “Login has expired, please login again” as the below:
Please support me this issue.
Thank you very much.
It looks like your nodes didn’t join together into a cluster, and run as three stand-alone nodes. This is likely due to service discovery settings being wrong. Can you double-check that K8S apiserver url is correct?
I tried create emqx cluster by helm. But when I run the cli $ helm install my-emqx emqx/emqx --set service.type=NodePort
has error as the below:
Error: unable to build kubernetes objects from release manifest: error validating “”: error validating data: ValidationError(StatefulSet.spec.template.spec.securityContext): unknown field “fsGroupChangePolicy” in io.k8s.api.core.v1.PodSecurityContext
kubectl version is v1.17
I can’t upgrade it because have many service is running on it.
Please help me.
So the screenshot of the emqx_ctl cluster status command confirms that the nodes didn’t form the cluster and operate one their own.
This is why you see “login is expired” errors when trying to use the dashboard: you’ve logged in on one of the nodes, but the other one isn’t aware of that.
Failure to cluster likely happens because the backplane ports are closed. EMQX uses ports 5369 and 4370 for broker-to-broker communication. These ports should be open. Unfortunately, I can’t tell how to do it in K8S.
I saw EMQX free version has 100k connections.
When I change to others image like: emqx-lastest or rc, cluster can’t run normally. Just see one pod when I run emqx_ctl cluster status.
Do you know this issue?
I saw this version is EMQX Enterprise 4.3.13.
I would like to use the open source edition can run cluster on k8s, connect to Mongo DB and has more 200 connections.
But I don’t know what version can do it.