<p>I am trying to install a RabbitMQ cluster on Kubernetes using offical docker image <code>rabbitmq:3.12.5-alpine</code>. I have a init container from where I am overriding the default configurations.</p>
<p>I can see RabbitMQ uses classic mirrored queue by default if a client creates a queue to publish into the nodes. But, This does not ensures persistence without setting certain policies through cli. The data gets deleted once a pod restarts. I want to set quorum queue to be default queue type for the cluster. Is there any way to override this setting from configuration file/environment variable when bootstrapping the cluster? I have checked out the official documentation but could not find any. Thanks in advance!</p>

Raihan Khan
<blockquote>
<p>I have checked out the official documentation but could not find any</p>
</blockquote>
<p>Actually, the official documentation does answer your question:</p>
<p><a href="https://www.rabbitmq.com/quorum-queues.html#declaring" rel="nofollow noreferrer">https://www.rabbitmq.com/quorum-queues.html#declaring</a></p>
<blockquote>
<p>To declare a quorum queue set the <code>x-queue-type</code> queue argument to <code>quorum</code> (the default is <code>classic</code>). This argument must be provided by a client at queue declaration time; it cannot be set or changed using a policy.</p>
</blockquote>
<p>Since this is a per-queue setting that happens at declaration time, there is currently <strong>no way</strong> to globally make all queues quorum queues.</p>
<hr />
<p><sub><b>NOTE:</b> Team RabbitMQ monitors the <code>rabbitmq-users</code> <a href="https://groups.google.com/forum/#!forum/rabbitmq-users" rel="nofollow noreferrer">mailing list</a> and only sometimes answers questions on StackOverflow.</sub></p>
