Merge pull request #259 from wanjunlei/release-2.5

release 2.5.1

CHANGLOG.md

@@ -1,3 +1,10 @@
+## v2.5.1 / 2024-04-03
+
+### Bugfix
+
+- fix bug regex silence will silence all alerts(#257). @wanjunlei
+
+
 ## v2.5.0 / 2024-03-21
 
 ### FEATURES

README.md

@@ -82,17 +82,17 @@ We assume you already have a Kubernetes cluster (v1.16+). You can install one us
 
 ```shell
 # Deploy CRDs and the Notification Manager Operator:
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.0/bundle.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.1/bundle.yaml
 # Deploy default template:
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.0/template.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.1/template.yaml
 # Deploy built-in language packs.
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.0/zh-cn.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.1/zh-cn.yaml
 ```
 
 #### Install with helm
 
 ```shell
-helm install notification-manager --create-namespace -n kubesphere-monitoring-system https://github.com/kubesphere/notification-manager/releases/download/v2.5.0/notification-manager.tgz
+helm install notification-manager --create-namespace -n kubesphere-monitoring-system https://github.com/kubesphere/notification-manager/releases/download/v2.5.1/notification-manager.tgz
 ```
 
 ### Configure NotificationManager 
@@ -103,7 +103,7 @@ ensures a deployment meeting the resource requirements is running.
 We should create a NotificationManager CR first, skip this when using helm install.
 
 ```shell
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.0/notification_manager.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.5.1/notification_manager.yaml
 ```
 
 ### Configure sender

RELEASE.md

@@ -18,6 +18,7 @@ This page describes the release process and the currently planned schedule for u
 | v2.3.0         | 2023-04-12             | leiwanjun (GitHub: @leiwanjun)      |
 | v2.4.0         | 2023-09-20             | leiwanjun (GitHub: @leiwanjun)      |
 | v2.5.0         | 2024-03-21             | leiwanjun (GitHub: @leiwanjun)      |
+| v2.5.1         | 2024-04-03             | leiwanjun (GitHub: @leiwanjun)      |
 
 
 # How to cut a new release

VERSION

@@ -1 +1 @@
-v2.5.0
+v2.5.1

config/bundle.yaml

@@ -8044,7 +8044,7 @@ spec:
             fieldRef:
               apiVersion: v1
               fieldPath: metadata.namespace
-        image: kubesphere/notification-manager-operator:v2.5.0
+        image: kubesphere/notification-manager-operator:v2.5.1
         imagePullPolicy: Always
         name: notification-manager-operator
         ports:

config/manager/kustomization.yaml

@@ -5,4 +5,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: kubesphere/notification-manager-operator
-  newTag: v2.5.0
+  newTag: v2.5.1

helm/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v1
-appVersion: 2.5.0
+appVersion: 2.5.1
 description: Notification Manager manages notifications in multi-tenant K8s environment. It receives alerts or notifications from different senders and then send notifications to various tenant receivers based on alerts/notifications' tenant label like "namespace". 
 name: notification-manager
-version: 2.5.0
+version: 2.5.1

helm/values.yaml

@@ -28,7 +28,7 @@ operator:
     operator:
       image:
         repo: kubesphere/notification-manager-operator
-        tag: v2.5.0
+        tag: v2.5.1
         pullPolicy: IfNotPresent
       resources:
         limits:
@@ -46,7 +46,7 @@ operator:
 notificationmanager:
   image:
     repo: kubesphere/notification-manager
-    tag: v2.5.0
+    tag: v2.5.1
     pullPolicy: IfNotPresent
   sidecar:
     image: