notification-manager icon indicating copy to clipboard operation
notification-manager copied to clipboard

K8s native notification management with multi-tenancy support

Results 24 notification-manager issues
Sort by recently updated
recently updated
newest added

版本: ksp v3.2.1 nm: v2.0.1 ![image](https://user-images.githubusercontent.com/20379897/169331989-f678c4fc-8230-44ff-9bd1-d5845102812b.png) receiver: ![image](https://user-images.githubusercontent.com/20379897/169332542-239983db-4bdb-455b-9b04-81d62a59166a.png) template: ![image](https://user-images.githubusercontent.com/20379897/169332899-863eabfc-aab7-4bd9-9ce4-fd697efeedd4.png) 麻烦看下是什么问题。哪里要修改吗?

Using curl to access the /api/v2/alerts interface to send notifications to Feishu, it takes about 40 seconds. I also tried using prometheus alertmanager as the sender, it's also slow. Is...

I learned from the doc that A tenant receiver only receives notifications from the namespaces that the tenant has access to. How do I give a tenant permission to access...

![image](https://user-images.githubusercontent.com/18796907/167537429-7d10289c-c7f5-4a05-b6b0-1cbccd722363.png) ![image](https://user-images.githubusercontent.com/18796907/167537010-cdd6e69f-d994-44c0-8a27-0421978de2fe.png) ![image](https://user-images.githubusercontent.com/18796907/167536839-1ed8aed9-45a4-4d97-9cd1-d9a00d46320d.png)

If a cluster uses [OwnerReferencesPermissionEnforcement](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#ownerreferencespermissionenforcement) then permission must be granted to finalizers on APIs it manages. https://sdk.operatorframework.io/docs/faqs/#after-deploying-my-operator-why-do-i-see-errors-like-is-forbidden-cannot-set-blockownerdeletion-if-an-ownerreference-refers-to-a-resource-you-cant-set-finalizers-on- We need to update the markers to include this sub resource for `NotificationManagers`.

In OKD/OpenShift hostPath mounts require additional privileges provided through SecurityContextContraints. We'd like to avoid the use of hostPath mounts so we do not need to grant unnecessary privileges to worklodas,...

Is the certificate used by NM [here](https://github.com/kubesphere/notification-manager/blob/master/config/cert/webhook-server-cert.yaml)? ![image](https://user-images.githubusercontent.com/39847025/168244117-05e9cb0f-6d0c-416a-be1c-795a4e01ecfe.png) ```bash ~]# kubectl get pod,svc -n monitoring | grep notif pod/notification-manager-deployment-7bffdfc9f-f99jh 1/1 Running 0 34m pod/notification-manager-operator-7cc9c59c75-fr759 2/2 Running 0 35m service/notification-manager-controller-metrics ClusterIP...

notification-manager-operator often Back-off, Log is leader election lost. What should I do ?

Whether kubesphere v3.4.0 is supported Change the log store to Elasticsearch with X-Pack Security enabled ?

the notification-manager version is v1.4.0 the error log ![image](https://github.com/kubesphere/notification-manager/assets/33190703/13090f0c-39de-4006-9906-464c2cf2c978) level=info ts=2023-08-21T07:31:32.217747701+08:00 caller=config.go:601 msg="resource change" op=add name=default-email-config level=info ts=2023-08-21T07:31:32.217852149+08:00 caller=config.go:601 msg="resource change" op=add name=default-wechat-config level=info ts=2023-08-21T08:13:13.761899063+08:00 caller=config.go:601 msg="resource change" op=add name=global-email-receiver...