Skip to content

Commit

Permalink
chore: dump version to 2.2.19
Browse files Browse the repository at this point in the history
Signed-off-by: Rory Z <[email protected]>
  • Loading branch information
Rory-Z committed Apr 9, 2024
1 parent 25fd5b8 commit ca67358
Show file tree
Hide file tree
Showing 23 changed files with 36 additions and 30 deletions.
14 changes: 10 additions & 4 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Release Note 🍻

EMQX Operator 2.2.18 has been released.
EMQX Operator 2.2.19 has been released.

## Supported version
+ apps.emqx.io/v2beta1
Expand All @@ -13,11 +13,17 @@ EMQX Operator 2.2.18 has been released.
+ EMQX at 4.4.14 and later
+ EMQX Enterprise at 4.4.14 and later

## Enhancements ✨
## Fixes 🛠

+ `apps.emqx.io/v2beta1 EMQX`.

+ Add podDisruptionBudget for EMQX customer resource.
+ Fix the issue that the EMQX operator can not update the K8s service port when the user changes EMQX's listener port by EMQX dashboard.

+ Fix the issue when the EMQX customer resources are updated with changes that affect both the statefulSet and the EMQX config, the statefulSet is updated last and this blocks the update process if the statefulSet changes are referenced in EMQX config. check: https://github.com/emqx/emqx-operator/issues/1027

## Other Changes ✨

+ Update `sigs.k8s.io/controller-runtime` version to 0.17

## How to install/upgrade EMQX Operator 💡

Expand All @@ -29,7 +35,7 @@ helm repo update
helm upgrade --install emqx-operator emqx/emqx-operator \
--namespace emqx-operator-system \
--create-namespace \
--version 2.2.18
--version 2.2.19
kubectl wait --for=condition=Ready pods -l "control-plane=controller-manager" -n emqx-operator-system
```

Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/deployment/on-aws-eks.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ The following is the relevant configuration of EMQX custom resources. You can se
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
## EMQX custom resources do not support updating this field at runtime
Expand Down
4 changes: 2 additions & 2 deletions docs/en_US/getting-started/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Alternatively, if you are interested in learning how to upgrade or uninstall EMQ
metadata:
name: emqx-ee
spec:
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
```

For more details about the EMQX CRD, please check the [reference document](../reference/v2beta1-reference.md).
Expand All @@ -101,7 +101,7 @@ Alternatively, if you are interested in learning how to upgrade or uninstall EMQ
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
```

For more details about the EMQX CRD, please check the [reference document](../reference/v2beta1-reference.md).
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-blueGreenUpdate.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ kind: EMQX
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
updateStrategy:
evacuationStrategy:
connEvictRate: 1000
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The main configuration file of EMQX is `/etc/emqx.conf`. Starting from version 5
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
imagePullPolicy: IfNotPresent
config:
data: |
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-core-replicant.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ There must be at least one Core node in the EMQX cluster. For the purpose of hig
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
replicas: 2
Expand Down
4 changes: 2 additions & 2 deletions docs/en_US/tasks/configure-emqx-license.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The following is the relevant configuration of EMQX Custom Resource. You can cho
license {
key = "..."
}
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
dashboardServiceTemplate:
spec:
type: LoadBalancer
Expand Down Expand Up @@ -150,7 +150,7 @@ The following is the relevant configuration of EMQX Custom Resource. You can cho
$ kubectl edit emqx emqx-ee
...
spec:
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
config:
data: |
license {
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-persistence.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ When the user configures the `.spec.coreTemplate.spec.volumeClaimTemplates` fiel
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
volumeClaimTemplates:
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-prometheus.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ kind: EMQX
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
```
Save the above content as `emqx.yaml` and execute the following command to deploy the EMQX cluster:
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The following is the relevant configuration of EMQX Custom Resource. You can cho
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
listenersServiceTemplate:
spec:
type: LoadBalancer
Expand Down
2 changes: 1 addition & 1 deletion docs/en_US/tasks/configure-emqx-tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ There are many types of Volumes. For the description of Volumes, please refer to
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
config:
data: |
listeners.ssl.default {
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/deployment/on-aws-eks.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ EMQX Operator 支持在 Amazon 容器服务 EKS(Elastic Kubernetes Service)
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
## 若开启了持久化,您需要配置 podSecurityContext,
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/deployment/on-huawei-cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ EMQX Operator 支持在华为云容器引擎(Cloud Container Engine,简称 C
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
## EMQX 自定义资源不支持在运行时更新这个字段
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/deployment/on-tencent-cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ EMQX Operator 支持在腾讯云容器服务(Tencent Kubernetes Engine,TKE
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
## EMQX 自定义资源不支持在运行时更新这个字段
Expand Down
4 changes: 2 additions & 2 deletions docs/zh_CN/getting-started/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@
metadata:
name: emqx-ee
spec:
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
```

并使用 `kubectl apply` 命令来部署 EMQX。
Expand Down Expand Up @@ -102,7 +102,7 @@
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
```

并使用 `kubectl apply` 命令来部署 EMQX。
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-blueGreenUpdate.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ kind: EMQX
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
updateStrategy:
evacuationStrategy:
connEvictRate: 1000
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ EMQX 主配置文件为 `etc/emqx.conf`,从 5.0 版本开始,EMQX 采用 [HO
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
config:
data: |
listeners.tcp.test {
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-core-replicant.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ EMQX 集群中至少要有一个 Core 节点,出于高可用的目的,EMQX O
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
replicas: 2
Expand Down
4 changes: 2 additions & 2 deletions docs/zh_CN/tasks/configure-emqx-license.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ EMQX 企业版 License 可以在 EMQ 官网免费申请:[申请 EMQX 企业版
license {
key = "${your_license_key}"
}
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
listenersServiceTemplate:
spec:
type: LoadBalancer
Expand Down Expand Up @@ -153,7 +153,7 @@ EMQX 企业版 License 可以在 EMQ 官网免费申请:[申请 EMQX 企业版
$ kubectl edit emqx emqx-ee
...
spec:
image: emqx/emqx-enterprise:5.1.0
image: emqx/emqx-enterprise:5.6
config:
data: |
license {
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-persistence.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
volumeClaimTemplates:
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-prometheus.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ kind: EMQX
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
coreTemplate:
spec:
ports:
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
listenersServiceTemplate:
spec:
type: LoadBalancer
Expand Down
2 changes: 1 addition & 1 deletion docs/zh_CN/tasks/configure-emqx-tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Volumes 的类型有很多种,关于 Volumes 描述可以参考文档:[Volum
metadata:
name: emqx
spec:
image: emqx:5.1
image: emqx:5
config:
data: |
listeners.ssl.default {
Expand Down

0 comments on commit ca67358

Please sign in to comment.