WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Kubernetes / Quick Tip - Access the RabbitMQ management UI when using the Kubernetes operator

Quick Tip - Access the RabbitMQ management UI when using the Kubernetes operator

12.03.2021 by William Lam // Leave a Comment

I was recently working with the RabbitMQ Cluster Kubernetes Operator, which provides an easy way to deploy and manage RabbitMQ clusters using Kubernetes (k8s). In fact, the VMware Event Broker Appliance (VEBA) solution also makes use of RabbitMQ operator as part of its backend infrastructure.

While troubleshooting my RabbitMQ deployment yesterday, I came to learn about a really useful tip in accessing the RabbitMQ management console UI which provides a number of useful pieces of information including resource utilization. Once logged in, we quickly found the issue which was due to memory pressure and once that was resolved, everything was working as expected.


I was not aware that RabbitMQ had this useful dashboard and that you could easily access it once you knew how to retrieve the credentials.

In my setup, I have the RabbitMQ cluster deployed in the vmware-functions k8s namespace and the name of the deployment is called veba-rabbit


Step 1 - Retrieve the username and password for your RabbitMQ cluster by running the following command and replace the namespace and deployment name with the one you used:

kubectl -n vmware-functions get secrets veba-rabbit-default-user -o json | jq -r '.data."default_user.conf"' | base64 -d


Step 2 - Enable port forwarding for the RabbitMQ Cluster on the default port 15672 by running the following command and replace the namespace and deployment name with the one you used:

kubectl -n vmware-functions port-forward services/veba-rabbit 15672


Step 3 - On your local computer, open a web browser to http://localhost:15672 and then login with the credentials from Step 1.

As mentioned earlier, VEBA also uses the RabbitMQ operator and if you wish to access the UI, mainly for educational and learning purposes, the instructions below can be used.

Step 1 - Enable TCP forwarding so that we can use SSH tunnel to access the RabbitMQ UI. SSH to VEBA appliance and edit /etc/ssh/sshd_config and comment AllowTcpForwarding no and then restart SSH by running systemctl restart sshd

Step 2 - Run the following to retrieve the RabbitMQ UI credentials:

kubectl -n vmware-system get secret veba-rabbit-default-user -o json | jq -r '.data."default_user.conf"' | base64 -d

Step 3 - Run the following command to port forward the RabbitMQ cluster:

kubectl -n vmware-system port-forward services/veba-rabbit 15672

Step 4 - On your local computer, open a new SSH session to your VEBA appliance specifying the following:

ssh root[at]veba.primp-industries.local -L 15672:localhost:15672 -N

Note: Once you successfully enter your VEBA credentials, the terminal will look like it is hanging and this is expected

Step 5 - Open a web browser to http://localhost:15672 and then login with the credentials from Step 2.

More from my site

  • VMware Event Broker Appliance (VEBA) v0.8.0
  • NSX Alarms in vCenter Server using vSphere Events in vSphere 8
  • Heads Up - Potential missing vCenter Server Events due to sequence ID overflow
  • vSphere Event-Driven Automation using VMware Event Router on VMware Cloud on AWS with Knative or AWS EventBridge
  • Integrating VMware Event Broker Appliance (VEBA) with Zapier

Categories // Kubernetes, VMware Tanzu Tags // RabbitMQ, VMware Event Broker Appliance

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...