Hello activemq list. New subscriber here.
We have ActiveMQ artemis running in Kubernetes clusters. I would like to expose the Artemis console using a Kubernetes Ingress. Basically, this handles the TLS termination for HTTPS, makes the application available at a specific hostname, and forwards the HTTP requests to port 8161 of the container running artemis. Using the Kubernetes ingress, I access the console using a URL like https://artemis.lb0020-ingress.stores.sherwin.com/ I can open the application, and get to the login page, but after logging in, it renders a basically empty shell with header, but nothing related to the broker in the console. When I use a different technique, i.e. Kubernetes port-fowarding, such that I can access the console at http://localhost:8161 then it works with no issues. In both cases, I’m accessing the same port of the same container. Digging deeper by watching the developer console in the web browser, I noticed a key difference in behavior when the javascript application attempts to make a request to the `/jolokia` endpoint. * When using http://localhost:8181 origin, (the one that works OK) it access /console/jolokia successfully. * When using the Kubernetes ingress, https://artemis.lb0020-ingress.stores.sherwin.com, the attempts to access jolokia fail. There are 2 attempts made, both fail and no further requests tried * /jolokia – yields 404 * /hawtio/jolokia – yields 404 I haven’t been fruitful with debugging the minified JS web application to see what’s going on here. I think only the minified JS is checked in to the central repository. Has anyone encountered this and solved it? Thanks, -- Chad Lauritsen IT Architect The Sherwin-Williams Company (216) 849-5945 Book Time with me<https://outlook.office.com/bookwithme/user/34f1d9682592497aa53064b106f4a...@sherwin.com?anonymous&ep=plink>
