How to increase the maximum length of additionalConfig in RabbitMQ Kubernetes Cluster Operator

Products

• RabbitMQ

Issue/Introduction

When deploying or configuring RabbitMQ on Kubernetes (such as OpenShift), users may need to provide custom configurations that exceed the 2000-character limit imposed on the additionalConfig field by the Kubernetes Cluster Operator.

Environment

 

• VMware Tanzu RabbitMQ for Kubernetes (versions prior to 4.0)

• RabbitMQ Cluster Operator (versions prior to 2.10.0)

• Kubernetes / OpenShift

 

Cause

The Custom Resource Definition (CRD) for the RabbitMQ cluster operator had a hardcoded character length limit of 2000 for the additionalConfig field, which restricted larger configuration payloads.

Resolution

Do not manually edit the CRD to bypass this limit. Instead, upgrade to a newer version of the product where this limitation has been addressed:

• The maximum length for additionalConfig has been increased and released in Cluster Operator version 2.10.0.

• This updated operator is included in VMware Tanzu RabbitMQ for Kubernetes 4.0.