Skip to content

rabbitmq/cluster-operator

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

…om/rabbitmq/rabbitmq-stream-go-client-1.3.0

Bump github.com/rabbitmq/rabbitmq-stream-go-client from 1.2.1 to 1.3.0
6a225d0

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
October 3, 2023 15:47
October 18, 2023 13:31
November 8, 2023 08:14
October 18, 2023 13:31
September 24, 2020 12:27
May 31, 2023 15:09
August 24, 2023 13:09
July 1, 2021 16:32
October 18, 2023 13:31

RabbitMQ Cluster Kubernetes Operator

Kubernetes operator to deploy and manage RabbitMQ clusters. This repository contains a custom controller and custom resource definition (CRD) designed for the lifecycle (creation, upgrade, graceful shutdown) of a RabbitMQ cluster.

Quickstart

If you have a running Kubernetes cluster and kubectl configured to access it, run the following command to install the operator:

kubectl apply -f https://github.com/rabbitmq/cluster-operator/releases/latest/download/cluster-operator.yml

Then you can deploy a RabbitMQ cluster:

kubectl apply -f https://raw.githubusercontent.com/rabbitmq/cluster-operator/main/docs/examples/hello-world/rabbitmq.yaml

Documentation

RabbitMQ Cluster Kubernetes Operator is covered by several guides:

In addition, a number of examples can be found in this repository.

The doc guides are open source. The source can be found in the RabbitMQ website repository under site/kubernetes.

Supported Versions

The operator deploys RabbitMQ 3.12.2 by default, and supports versions from 3.9.9 upwards. The operator requires Kubernetes 1.19 or newer.

Versioning

RabbitMQ Cluster Kubernetes Operator follows non-strict semver.

The versioning guidelines document contains guidelines on how we implement non-strict semver. The version number MAY or MAY NOT follow the semver rules. Hence, we highly recommend to read the release notes to understand the changes and their potential impact for any release.

Contributing

This project follows the typical GitHub pull request model. Before starting any work, please either comment on an existing issue, or file a new one.

Please read contribution guidelines if you are interested in contributing to this project.

Releasing

To release a new version of the Cluster Operator, create a versioned tag (e.g. v1.2.3) of the repo, and the release pipeline will generate a new draft release, alongside release artefacts.

License

Licensed under the MPL, same as RabbitMQ server.

Copyright

Copyright 2020-2023 VMware, Inc. All Rights Reserved.

Go Report Card