Releases · freepik-company/notifik

Refactor integrations in config file:
- This section was converted into a list of integrations allowing the users have several of the same type with different parameters
- There is a new field verb on webhooks integration to specify the method of the HTTP request
- There is a new field validator to specify a validator helper for the webhook. By the moment we crafted only one for Alertmanager that will throw a log in case the final message that should be sent does not fit Alertmanager incoming syntax requirements
To select an integration for sending notifications, there is a new field in Notification objects under message.integration to specify its name. It matches with the name of the integration under config file
Alertmanager integration was adopted into webhooks integration. It makes more sense as this is just another type of webhook
The field message.reason was deleted from Notification objects. The reason for this is to keep the spec as clear as possible, having just the fields that are really needed, avoiding doing tricks under the hood that the user does not expects

Contributors:
@achetronic

achetronic

Assets 16

29 Sep 04:21

notifik-helm-chart-0.8.0

A Helm chart for Notifik, a Kubernetes operator to watch groups of resources and send notifications if conditions are met (realtime)

Assets 3

08 Apr 15:18

achetronic

v0.7.0

Changes:

globals.DeleteWatcherFromWatcherPool() is replaced by globals.DisableWatcherFromWatcherPool() to avoid some concurrency problems. From now, empty watchers will be killed not to consume resources, but their registration will be kept in memory. This way we avoid collisions between controller.NotificationsReconciler and xyz.WorkloadController during their operation and checks in common places

Contributors:
@achetronic

achetronic

Assets 16

08 Apr 09:09

achetronic

v0.6.0

Changes:

--informer-seconds-to-resync is now --informer-duration-to-resync to simplify some pieces of code and give more freedom to the users at the same time
📜 Update README to include changes related to main templating scope . := dict "eventType" (string) "object" (dict) "previousObject" (dict)

Contributors:
@achetronic

achetronic

Assets 16

08 Apr 02:42

achetronic

v0.5.0

Features:

🤯 Add more data available to the conditions/message template. Previously the main scope . on templating included only the object triggering the event. From this release this was replaced by a more complete object . = {eventType, object, previousObject}. This will help to handle some use cases where it's needed to distinguish the events to send notifications. For example, like using Notifik to set markers on Grafana when a new ReplicaSet is created
❤️ Replace Watchers with RetryWatchers and Informers. Previously, resources in Kubernetes were watched using pure client-go watchers. On network issues or Kubernetes API server timeouts, watcher was simply recreated, triggering all the events again, spamming Kubernetes API server from time to time. Now, this was replaced by RetryWatchers and Informers, that are two newer patterns to do the same with some retries and cache in the middle. This is intended to hide this problems from the final user, being much more resilient and causing less spam to the API. Both are included (Informers are used by default) and you can chose your favorite strategy with a flag
🏳️ Add several flags
- --use-watchers to enable using RetryWatchers instead of Informers.
- --informer-seconds-to-resync to set the amount of seconds to wait before resyncing all the objects when using Informers
- --watcher-events-per-second to replace previous --events-per-second
📜 Update README to include changes