<div><img width="300" height="300" src="https://blogs.vmware.com/wp-content/uploads/2026/01/vmw-prod-icon-vSphere-kubernetes-service-rgb-e1769030511461.png" class="attachment-medium size-medium wp-post-image" alt="" style="margin-bottom: 10px;" decoding="async" loading="lazy" srcset="https://blogs.vmware.com/cloud-foundation/wp-content/uploads/sites/75/2026/01/vmw-prod-icon-vSphere-kubernetes-service-rgb-e1769030511461.png 300w, https://blogs.vmware.com/cloud-foundation/wp-content/uploads/sites/75/2026/01/vmw-prod-icon-vSphere-kubernetes-service-rgb-e1769030511461.png?resize=150,150 150w" sizes="auto, (max-width: 300px) 100vw, 300px" /></div><p>Modern applications depend on reliable messaging. Getting that infrastructure deployed and operated should be straightforward, not a separate engineering project. Running <a href="https://www.vmware.com/products/cloud-infrastructure/vsphere-kubernetes-service"><strong>VMware vSphere Kubernetes Service (VKS)</strong> </a>with <a href="https://www.vmware.com/products/app-platform/tanzu-data-intelligence/rabbitmq"><strong>Tanzu RabbitMQ</strong></a> does exactly that.</p> <p>This setup lets teams run RabbitMQ on VKS, a CNCF-certified Kubernetes runtime that is built-in with <a href="https://www.vmware.com/products/cloud-infrastructure/vmware-cloud-foundation"><strong>VMware Cloud Foundation (VCF)</strong>,</a> without introducing a new operational model or tooling stack. You get Kubernetes where it makes sense, while keeping vSphere as the control plane your operators already understand.</p> <h2 class="wp-block-heading has-vivid-cyan-blue-color has-text-color has-link-color wp-elements-4a3c7d440ce2af296fd9504d8ada80c5" id="h-why-run-tanzu-rabbitmq-on-vks"><strong>Why run Tanzu RabbitMQ on VKS?</strong></h2> <ul class="wp-block-list"> <li><strong>Operational continuity</strong><strong><br /></strong>VKS integrates directly with vSphere. Cluster lifecycle, networking, storage, and access controls follow the same patterns your infrastructure team already uses. No parallel platform to manage.</li> <li><strong>Lower operational overhead</strong><strong><br /></strong>You avoid retraining teams or adding new management layers. Kubernetes runs inside your existing private cloud, reducing both ongoing cost and operational risk.</li> <li><strong>Messaging features that matter</strong><strong><br /></strong>Tanzu RabbitMQ includes capabilities such as Warm Standby Replication and intra-cluster compression. These directly improve availability, recovery behavior, and throughput in production environments.</li> <li><strong>Managed lifecycle</strong><strong><br /></strong>VKS automates cluster creation, upgrades, and patching. RabbitMQ runs on a maintained Kubernetes substrate, keeping both security and reliability predictable over time.</li> </ul> <h2 class="wp-block-heading has-vivid-cyan-blue-color has-text-color has-link-color wp-elements-9dc3c920456f290dcffd32b6417bf011" id="h-a-validated-approach"><strong>A Validated Approach</strong></h2> <p>For more details, check out <a href="https://www.vmware.com/docs/isv-tanzu-rmq-vks-vcf">this </a>reference architecture. It has been validated as a complete stack, from infrastructure through messaging. It focuses on predictable operations, clear failure modes, and repeatable deployment rather than experimentation.</p> <p>If you want a practical way to run enterprise messaging on Kubernetes without re-platforming your operations team, this approach works!</p> <p></p><p>The post <a href="https://blogs.vmware.com/cloud-foundation/2026/01/21/scaling-messaging-with-confidence-vmware-vsphere-kubernetes-service-and-tanzu-rabbitmq/">Scaling Messaging with Confidence: VMware vSphere Kubernetes Service and Tanzu RabbitMQ</a> appeared first on <a href="https://blogs.vmware.com/cloud-foundation">VMware Cloud Foundation (VCF) Blog</a>.</p>
Modern applications depend on reliable messaging. Getting that infrastructure deployed and operated should be straightforward, not a separate engineering project. Running VMware vSphere Kubernetes Service (VKS) with Tanzu RabbitMQ does exactly that.
This setup lets teams run RabbitMQ on VKS, a CNCF-certified Kubernetes runtime that is built-in with VMware Cloud Foundation (VCF), without introducing a new operational model or tooling stack. You get Kubernetes where it makes sense, while keeping vSphere as the control plane your operators already understand.
Why run Tanzu RabbitMQ on VKS?
- Operational continuity
VKS integrates directly with vSphere. Cluster lifecycle, networking, storage, and access controls follow the same patterns your infrastructure team already uses. No parallel platform to manage. - Lower operational overhead
You avoid retraining teams or adding new management layers. Kubernetes runs inside your existing private cloud, reducing both ongoing cost and operational risk. - Messaging features that matter
Tanzu RabbitMQ includes capabilities such as Warm Standby Replication and intra-cluster compression. These directly improve availability, recovery behavior, and throughput in production environments. - Managed lifecycle
VKS automates cluster creation, upgrades, and patching. RabbitMQ runs on a maintained Kubernetes substrate, keeping both security and reliability predictable over time.
A Validated Approach
For more details, check out this reference architecture. It has been validated as a complete stack, from infrastructure through messaging. It focuses on predictable operations, clear failure modes, and repeatable deployment rather than experimentation.
If you want a practical way to run enterprise messaging on Kubernetes without re-platforming your operations team, this approach works!
The post Scaling Messaging with Confidence: VMware vSphere Kubernetes Service and Tanzu RabbitMQ appeared first on VMware Cloud Foundation (VCF) Blog.
