Connection and Queue tab details are missing when rabbitmq is deployment in kubernetes environment #3054
-
We have two environments where Rabbitmq servers are deployed one is docker-compose and other is kubernetes clusters, we have same configurations for both the environments but we are not getting details when clicking on "Connection" and "Queue" tab in kubernetes environment but its working in docker-compose. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 7 replies
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
There isn't a whole lot of information to work with. You haven't shared any details on how you provisioned any of the clusters, I'd start with exploring the responses, perhaps they are not JSON but some kind of "access refused" HTML page served in your environment. Browser developer tools is the easiest option. |
Beta Was this translation helpful? Give feedback.
-
You perform URL rewriting on your Ingress so I'd expect that to be the culprit. Check https://www.rabbitmq.com/management.html#path-prefix |
Beta Was this translation helpful? Give feedback.
-
I'd try this:
since you are rewriting the URLs to |
Beta Was this translation helpful? Give feedback.
-
You configured your Can I ask you to test whether the Management UI works correctly when you connect directly to the RabbitMQ node? If yes - there is no issue with RabbitMQ but purely with how you forward/rewrite traffic to it. |
Beta Was this translation helpful? Give feedback.
You perform URL rewriting on your Ingress so I'd expect that to be the culprit. Check https://www.rabbitmq.com/management.html#path-prefix