release v2.6.1 (#304)

Signed-off-by: wanjunlei <wanjunlei@kubesphere.io>

Author: wanjunlei

CHANGLOG.md

@@ -1,3 +1,9 @@
+## v2.6.1 / 2026-03-20
+
+### Enhancements
+
+- Optimize the alarm tenant matching mechanism (#302) @wanjunlei
+
 ## v2.6.0 / 2025-06-30
 
 ### Enhancements

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.6.0/bundle.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.1/bundle.yaml
 # Deploy default template:
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.0/template.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.1/template.yaml
 # Deploy built-in language packs.
-kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.0/zh-cn.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.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.6.0/notification-manager.tgz
+helm install notification-manager --create-namespace -n kubesphere-monitoring-system https://github.com/kubesphere/notification-manager/releases/download/v2.6.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.6.0/notification_manager.yaml
+kubectl apply -f https://github.com/kubesphere/notification-manager/releases/download/v2.6.1/notification_manager.yaml
 ```
 
 ### Configure sender

RELEASE.md

@@ -21,6 +21,7 @@ This page describes the release process and the currently planned schedule for u
 | v2.5.1         | 2024-04-03             | leiwanjun (GitHub: @leiwanjun)      |
 | v2.5.2         | 2024-04-14             | leiwanjun (GitHub: @leiwanjun)      |
 | v2.6.0         | 2025-06-30             | Gentleelephant (GitHub: @Gentleelephant) |
+| v2.6.1         | 2026-03-20             | leiwanjun (GitHub: @leiwanjun)      |
 
 # How to cut a new release
 

VERSION

@@ -1 +1 @@
-v2.6.0
+v2.6.1

config/samples/notification_manager.yaml

@@ -11,7 +11,7 @@ spec:
     requests:
       cpu: 100m
       memory: 20Mi
-  image: kubesphere/notification-manager:v2.6.0
+  image: kubesphere/notification-manager:v2.6.1
   imagePullPolicy: Always
   serviceAccountName: notification-manager-sa
   portName: webhook

helm/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v1
-appVersion: 2.6.0
+appVersion: 2.6.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.6.0
+version: 2.6.1

helm/values.yaml

@@ -27,7 +27,7 @@ operator:
     operator:
       image:
         repo: kubesphere/notification-manager-operator
-#        tag: v2.6.0
+#        tag: v2.6.1
         pullPolicy: IfNotPresent
       resources:
         limits:
@@ -45,7 +45,7 @@ operator:
 notificationmanager:
   image:
     repo: kubesphere/notification-manager
-#    tag: v2.6.0
+#    tag: v2.6.1
     pullPolicy: IfNotPresent
   sidecar:
     image: