A Kubernetes Operator for EMQX
The EMQX Operator provides Kubernetes native deployment and management of EMQX, including EMQX Broker and EMQX Enterprise. The purpose of this project is to simplify and automate the configuration of the EMQX cluster.
The EMQX Operator includes, but is not limited to, the following features:
-
Kubernetes Custom Resource: Deploy and manage EMQX Cluster with pre-defined custom resources.
-
Simplified Deployment Configuration: Configure the fundamentals of EMQX Cluster, including persistence, configuration, license, etc., in a Kubernetes-native way.
For an introduction to the EMQX Operator, see the introduction.
The EMQX Operator requires a Kubernetes cluster of version >=1.20.0.
A core feature of the EMQX Operator is to monitor the Kubernetes API server for changes to specific objects and ensure that the running EMQX deployments match these objects. The Operator acts on the following custom resource definitions (CRDs).
For the example of EMQX, see the emqx-full.yaml.
The EMQX Operator automatically detects changes on any of the above custom resource objects and ensures that running deployments are kept in sync with the changes.
| EMQX 4.2 latest | EMQX 4.3 latest | EMQX 4.4 latest | EMQX 5.0 latest | |
|---|---|---|---|---|
| EMQX Operator 1.1 latest | ✓ | ✓ | ||
| EMQX Operator 1.2 latest | ✓ | |||
| EMQX Operator 2.0 latest | ✓ | ✓ |
For more information on getting started, see the getting started.
| Public Cloud Platform | Deployment Guide |
|---|---|
| AWS | EKS |
| Azure | Azure |
| Alibaba Cloud | ACK |
| Huawei | CCE |
| Tencent | TKE |
- Golang environment
- docker (used for creating container images, etc.)
- Kubernetes cluster
Many files (API, config, controller, hack,...) in this repository are auto-generated. Before proposing a pull request:
- Commit your changes.
makeandmake manifests- Commit the generated changes.
Check the troubleshooting documentation for common issues and frequently asked questions (FAQ).