You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a notification is deleted it's not reflected in "kube-notifier-controller" - resulting in notifications being send after deletion.
To Reproduce
Create notification. E.g
kubectl apply -f hello-notifier.yaml -n hello-app
.. trigger notification condition to check a notification is send.
Trigger notification condition again, resulting in notification is being send again, even if it's been deleted.
Expected behavior
When a given notification is deleted, kube-notifier-controller should not send any notifications of given kind.
Additional context
In order to update "kube-notifier-controller" with latest changes (notification deletion), i had to restart controller manually (by deleting pod)
The text was updated successfully, but these errors were encountered:
@sarabala1979 , haven't much of golang experience, and not sure how much time I will have for it, but if you have time to set me up and point me in the right direction I'm willing to give it a try.
Describe the bug
When a notification is deleted it's not reflected in "kube-notifier-controller" - resulting in notifications being send after deletion.
To Reproduce
Create notification. E.g
kubectl apply -f hello-notifier.yaml -n hello-app
.. trigger notification condition to check a notification is send.
Delete notification:
kubectl delete notifications.argoproj.io hello-notifier -n hello-app
Trigger notification condition again, resulting in notification is being send again, even if it's been deleted.
Expected behavior
When a given notification is deleted, kube-notifier-controller should not send any notifications of given kind.
Additional context
In order to update "kube-notifier-controller" with latest changes (notification deletion), i had to restart controller manually (by deleting pod)
The text was updated successfully, but these errors were encountered: