-
Notifications
You must be signed in to change notification settings - Fork 69
Management Console login fails #12
Comments
It seems the issue is related to jolokia which does not allow incoming requests from outside the cluster, I found that JOLOKIA_ALLOW_ORIGIN attribute can be sent when starting docker, can we use it through helm chart installation? |
I actually never envisioned the console to be exposed publicly. I have been using it mostly through edit: I am indeed interested because I've been thinking about a network policy for a while, and the console was the first thing I was meaning to restrict. |
Hi @tiagokos - not sure if this is still an issue for you, but.. in our ActiveMQ deployment we have this working, without changes to Jolokia. The problem we found was the fact that the connection to the cluster is being load-balanced (round robin), so that the connection never 'sticks' to a particular console instance. The current charts add a 'ClientIP' affinity which should fix this. (https://github.com/vromero/activemq-artemis-helm/blob/master/activemq-artemis/templates/service.yaml#L28) |
@vromero , thank you very much. |
Hello, I deployed your helm chart on our kubernetes cluster, added ingress on the top of that in order to access http://activemq-artemis.devel.fdp.eit.zone/console/login
The only problem is that the username / password specified does not log in correct, after filling in the login fields on the login page, the management console opens for a second and goes back to the first page in a second.
On network tab I can see some forbidden calls to http://activemq-artemis.devel.fdp.eit.zone/console/refresh
Do you have any ideas?
The text was updated successfully, but these errors were encountered: