VMware Tanzu RabbitMQ for VMs Release Notes
Note: Pivotal Platform is now part of VMware Tanzu. In v1.20 and later, VMware Tanzu RabbitMQ [VMs] is named VMware Tanzu RabbitMQ for VMs.
For product versions and upgrade paths, see Upgrade Planner.
Release Date: December 14, 2020
New features and changes in this release:
RabbitMQ Web STOMP plugin for on-demand instances: You can enable this plugin for on-demand instances including instances with TLS and service-gateway.
OAuth for apps: Apps can now authenticate with RabbitMQ using the OAuth client flow. For more information, see Enabling OAuth for Apps.
Option to enforce OAuth for on-demand instances: When OAuth is enforced, the tile does not return RabbitMQ user credentials in the binding, making OAuth the only source for application authentication and authorization. There is also an option to enable OAuth without enforcing it. This still returns RabbitMQ user credentials in the binding while also having the OAuth plugin enabled for the instance. For more information, see Enabling OAuth for RabbitMQ.
Includes the UAA URL in service keys and bindings when OAuth is enabled: This helps apps to fetch the OAuth token from UAA. For more information, see Enabling OAuth for RabbitMQ.
Option to limit the TLS versions enabled for on-demand instances: Tanzu RabbitMQ v1.21.0 supports TLS v1.0, v1.1, and v1.2 (default). Additionally, you can now select the TLS versions to enable in RabbitMQ. This disables the other TLS versions.
To configure TLS, follow the procedure in Configure Security.
For more information about disabling TLS versions, see the RabbitMQ documentation.
Option to add VM extensions to on-demand instances: You can provide a list of VM extensions to add to on-demand service instances. This feature enables you to exclude VMs hosting on-demand service instances from being dynamically provisioned by an underlying IaaS, among other capabilities. For more information, see Configure Global Settings in Installing and Configuring the On-Demand Service.
Improved internal security for service-gateway: For delete operations, the on-demand service broker now communicates with routing components over mutual TLS.
This release has the following issue:
- Changing the Erlang cookie can cause failed deployments: Changing the Erlang cookie value requires cluster downtime and can result in failed deployments. For more information, see Changing the Erlang Cookie Value Known Issue.
The following components are compatible with this release:
|VMware Tanzu Application Service for VMs||2.7.x, 2.8.x, 2.9.x, 2.10.x|
* For more information, see the v3.8.9 GitHub documentation.
To view the release notes for another product version, select the version from the dropdown at the top of this page.