If the embedded web server which serves the console (as configured in bootstrap.xml) is bound to localhost then it will never be accessible from a remote machine. You need to bind it to an IP or hostname which is externally accessible.
Justin On Tue, Aug 17, 2021 at 2:58 PM Thai Le <lnthai2...@gmail.com> wrote: > Hello, > > I am not sure if questions regarding Artemis cloud can be asked here but > since i found no mailing list for artemis cloud and the slack channel needs > an invitation to join I'm gonna try my luck here. > > I installed the Artemis operator and an ActiveMQArtemis with a deployment > plan of 2 brokers on my single node kubernetes (docker-desktop), here is > the deployment: > > apiVersion: broker.amq.io/v2alpha5 > kind: ActiveMQArtemis > metadata: > name: ex-aao > spec: > adminUser: brokerAdmin > adminPassword: verySecret > deploymentPlan: > size: 2 > image: placeholder > podSecurity: > runAsUser: 0 > console: > expose: true > sslEnabled: false > > The 2 brokers are running and I can curl the web console from another pod > in the same kubernetes cluster. However, I cannot access the web console > from my desktop (http://localhost:8161/console). I also tried to port > forward requests to port 8161 from my desktop to one of the 2 artemis pods > but it does not work either. > > I would appreciate it if anyone could give me a hint as to what may be > wrong or a direction to artemis cloud mailing list > > Thai Le >
