Skip to content

Releases: kubesphere/notification-manager

v2.0.1

13 May 06:36
Compare
Choose a tag to compare

BUGFIX

  • Fix bug that the dispatcher worker routine is not released (#136). @gliffcheung
  • Fix bug that the template could not generate notifications correctly (#139). @wanjunlei
  • Fix bug that the namespace cannot be specified when installing with helm (#141). @wanjunlei

v2.0.0

18 Apr 07:25
f22102b
Compare
Choose a tag to compare

FEATURES

  • Support to route the specific notifications to the specific receivers using Router CRD (#121). @wanjunlei
  • Support to mute specific notifications for a given period using Silence CRD (#121). @wanjunlei
  • Add support to send notifications to Feishu (#124). @wanjunlei
  • Support the dynamic modification of the template (#123). @wanjunlei
  • Add e2e tests with GitHub action (#111). @zhu733756
  • Add support to build and push a container image after PR is merged (#122). @wenchajun

Enhancement

  • Refactor the cache mechanism of receiver and config (#118). @wanjunlei
  • Add support for custom the pushover title using a template (#128). @wanjunlei
  • Optimize the mechanism of reloading the receivers and configs after Notification Manager CR changed (#127). @wanjunlei
  • Support to get KubeSphere cluster name from configmap (#125). @wanjunlei

BUGFIX

  • Resolve the problem of filtered notifications being recorded in the notification history (#117). @wanjunlei

v1.4.0

20 Oct 02:42
2077f77
Compare
Choose a tag to compare

FEATURES

  • Support collecting notification history. #102
  • Add tenant sidecar for KubeSphere v3.2.0. #105

UPGRADE & BUGFIX

  • Fix the bug that the error is not returned to the caller during notification setting verification. #104
  • Fix WeChat alert selector doesn't work. #109

v1.3.0

12 Aug 06:00
9d22c1f
Compare
Choose a tag to compare

v1.3.0 / 2021-08-10

FEATURES

CHANGE

  • Adjust alertmanager integration guide.
  • Adjust hostpath host-time (mounts /etc/localtime) to read-only mode.

v1.2.0

15 Jul 08:31
Compare
Choose a tag to compare

FEATURES

  • Add support to verify the receivers and configs. @wanjunlei
  • Add support to get tenant info from a sidecar. @wanjunlei
  • Add support to send notifications to SMS platforms (Aliyun & Tencent). @zhu733756
  • Add support to send DingTalk notifications in markdown format. @happywzy
  • Add support to send Wechat notifications in markdown format. @wanjunlei
  • Add support to send Email notifications in text format. @wanjunlei
  • Now DingTalk chatbot can @ someone in the notification messages. @happywzy
  • Now Every receiver can set a template for itself. @wanjunlei
  • Add an API to send notifications directly. @wanjunlei

UPGRADE & BUGFIX

  • Upgrade the crd version to v2beta2.
  • Fix some bugs.

v1.0.0

23 Apr 03:18
2ee63df
Compare
Choose a tag to compare

UPGRADE & ENHANCEMENT

  • All config crds are aggregated into a crd named Config.
  • All receivers crds are aggregated into a crd named Receiver.
  • Now the Config, Receiver, and NotificationManager are cluster scoped crd.
  • Now the namespace of the secret can be specified in SecretKeySelector .
  • Move the configuration of DingTalk chatbot from dingtalk config to dingtalk receiver.
  • Move the chatid of DingTalk conversation from dingtalk config to dingtalk receiver.
  • Now the chatid of DingTalk conversation is an array types, and renamed to chatids.
  • Now the port of email smartHost is an integer type.
  • Now the channel fo slack is an array types, and renamed to channels.
  • Move the configuration of webhook from webhook config to webhook receiver.
  • Now the toUser, toParty, toTag of wechat receiver are array type.
  • Fix some bugs.

v1.0.0-rc.0

08 Apr 03:25
5fd95ce
Compare
Choose a tag to compare

UPGRADE & ENHANCEMENT

  • All config crds are aggregated into a crd named Config.
  • All receivers crds are aggregated into a crd named Receiver.
  • Now the Config, Receiver, and NotificationManager are cluster scoped crd.
  • Now the namespace of the secret can be specified in SecretKeySelector .
  • Move the configuration of DingTalk chatbot from dingtalk config to dingtalk receiver.
  • Move the chatid of DingTalk conversation from dingtalk config to dingtalk receiver.
  • Now the chatid of DingTalk conversation is an array types, and renamed to chatids.
  • Now the port of email smartHost is an integer type.
  • Now the channel fo slack is an array types, and renamed to channels.
  • Move the configuration of webhook from webhook config to webhook receiver.
  • Now the toUser, toParty, toTag of wechat receiver are array type.
  • Fix some bugs.

v0.8.0

04 Mar 09:31
67a4c9b
Compare
Choose a tag to compare

UPGRADE & ENHANCEMENT

  • Change all CRDS to cluster scope CRD.
  • Now the receiver can filter notifications with a LabelSelector
  • Fix some bugs.

v0.7.0

04 Dec 07:14
Compare
Choose a tag to compare

UPGRADE & ENHANCEMENT

  • Add a label named cluster to notifications which used to identify the cluster that generated the notification. #50
  • Add a notification adapter sink which receive notifications from notification manager and then send it to a TCP endpoint. #51
  • Fix some bugs.

v0.6.0

05 Nov 10:28
5ceddb2
Compare
Choose a tag to compare

UPGRADE & ENHANCEMENT

  • Add support of webhook and DingTalk. #36
  • Refactored the code of receivers managed, simplified the development for the new receiver. #36
  • Now it supports to mount volumes to the notification manager. #36
  • Now it supports to add args to the notification manager. #36
  • Now it supports to customize the notification template. #36
  • Use multiple goroutines to send notifications to optimize performance. #40
  • Aggregate the notifications sending to wechat and dingtalk, reduce the API calls. #40