Create Instance

RabbitMQ is a popular message queue middleware that features an efficient and reliable message asynchronous delivery mechanism. It is mainly used for data exchange and transmission between different systems and has a wide range of applications in various fields such as enterprise solutions, financial payments, telecommunications, e-commerce, social networking, instant messaging, video, the Internet of Things, and vehicle networking.

In the current version, the following RabbitMQ versions are supported: 3.12 and 4.2. RabbitMQ 3.8.16 is no longer supported in v4.2.x. The instance creation process uses 4.2 as an example.

Version Suggestion

When selecting a version, use the latest supported version whenever possible. 4.2 is recommended for new deployments:

4.2 includes newer community fixes and ongoing feature evolution.
If you are running 3.12, plan and validate migration to 4.2 according to your business window.

Create RabbitMQ Instance

Prerequisites

Please ensure that there is an available storage class in the current cluster and that there is sufficient available space.

Procedure

CLI

Web Console

Create a RabbitMQ instance via CLI:

$ cat << EOF | kubectl -n default create -f -
apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  name: rrrr
spec:
  affinity:
    podAntiAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchLabels:
              app.kubernetes.io/name: cluster-in
          topologyKey: kubernetes.io/hostname
  persistence:
    storage: 1Gi
    storageClassName: sc-topolvm
  rabbitmq:
    additionalConfig: |-
      channel_max=1000
      cluster_keepalive_interval=10000
      collect_statistics=none
      collect_statistics_interval=5000
      default_vhost=/
      delegate_count=16
      disk_free_limit.absolute=50MB
      handshake_timeout=10000
      heartbeat=60
      max_message_size=134217728
      mirroring_sync_batch_size=4096
      mnesia_table_loading_retry_limit=10
      mnesia_table_loading_retry_timeout=30000
      num_acceptors.tcp=10
      queue_index_embed_msgs_below=4096
      raft.wal_max_size_bytes=64000000
      vm_memory_calculation_strategy=allocated
      vm_memory_high_watermark.relative=0.4
      vm_memory_high_watermark_paging_ratio=0.5
  replicas: 3
  resources:
    limits:
      cpu: 1
      memory: 2Gi
    requests:
      cpu: 1
      memory: 2Gi
  service:
    type: ClusterIP
  upgradeOption:
    autoUpgrade: false
  version: "4.2"
EOF

For detailed field information, please refer to RabbitMQ API Documentation.

After the instance is created, you can view the instance with the following command:

$ kubectl -n default get rabbitmqclusters
NAME   AGE
rrrr   74s

You can use the following custom command to view the status of the instances in bulk:

$ kubectl -n default get rabbitmqclusters rrrr -o custom-columns='NAME:.metadata.name,PHASE:.status.phase,USER SECRET:.status.defaultUser.secretReference.name'
NAME   PHASE    USER SECRET
rrrr   Active   rrrr-default-user

The meaning of the output table fields is as follows:

Field	Description
NAME	Instance name
PHASE	Instance status, which can be in the following states: `Creating`: The instance is creating resources and initializing the cluster `Updating`: The instance configuration is being updated `Active`: The instance is in service status `Failed`: The instance encountered an error during initialization or update `Unknown`: The instance is in an unrecognized state `Paused`: The instance is paused and the related Pods have been shut down
USER SECRET	Secret that stores the default user account information

In the left navigation bar, click RabbitMQ.
Click on the namespace name.
Click Create RabbitMQ Instance.
Refer to the following instructions to configure the relevant parameters.

Configuration	Parameter Item	Description
Parameter Configuration	Parameter Template	You can select a system or custom parameter template; for custom templates, please refer to Parameter Templates.
Resource Configuration	Storage Class	If no available storage class is found in the dropdown list, please contact the platform administrator to add one.
Connection Configuration	Specify Host Port	This configuration option appears when selecting external cluster access. Note: When updating the instance, the port does not support swapping. If you need to swap ports, you can first update to another unused port and then respecify.
Scheduling Configuration	Node Labels	This filters available nodes in the current cluster by labels. Pods will be scheduled to available nodes. Note: After the instance is created, this configuration is no longer modifiable.
Scheduling Configuration	Pod Tolerations	If the available nodes have been tainted, only Pods with tolerations will tolerate these taints and may be scheduled to nodes matching the Pod tolerations and node taints. The matching rules are as follows: Equal: When the key, value, and effect of the Pod toleration exactly match the corresponding values in the node taint, the Pod will tolerate the node taint. Exists: When the key and effect of the Pod toleration are consistent with the corresponding values in the node taint, the Pod will tolerate the node taint. Description: The effect determines whether Pods that do not tolerate node taints will be assigned to nodes with taints. For example, if the effect is NoExecute, only pods that tolerate the taints can be scheduled, and pods already running on the node that do not tolerate the taints will be evicted. For more information on matching rules, refer to Kubernetes Official Documentation.

Click Create. Wait for the instance status to change to Running, indicating that the instance has been created successfully.
Proceed with message delivery.

Tip

For the connection methods of business applications accessing RabbitMQ instances, please refer to Select Connection Address and Configure Connection Method.

#Create Instance

#TOC

#Create RabbitMQ Instance

#Prerequisites

#Procedure

Create Instance

TOC

Create RabbitMQ Instance

Prerequisites

Procedure