Dis<p><span>Looks like it is getting replaced. (I'm disappointed in the 44 of you that want to give a hostile company tons of free labor. Do better. </span>:rick:<span>)<br><br>If anyone else uses </span><a href="https://infosec.town/tags/Botkube" rel="nofollow noopener" target="_blank">#Botkube</a><span> and missed the announcement, sorry to be the bearer of bad news: </span><a href="https://github.com/kubeshop/botkube/releases/tag/v1.9.0" rel="nofollow noopener" target="_blank">github.com/kubeshop/botkube/releases/tag/v1.9.0</a><span><br><br>I already implemented about 60% of the "event watcher" pipeline in </span><a href="https://infosec.town/tags/nodered" rel="nofollow noopener" target="_blank">#nodered</a><span> so maybe I'll just finish that out. I needed nodered anyway because Botkube's webhook "support" is total amateur hour. If I had to guess, I would say it is an internal structure they just throw at the endpoint with no documentation. It changes, sometimes dramatically, from version to version.<br><br>Anyone know of a better event monitor for </span><a href="https://infosec.town/tags/k8s" rel="nofollow noopener" target="_blank">#k8s</a><span> </span><a href="https://infosec.town/tags/homelab" rel="nofollow noopener" target="_blank">#homelab</a><span> </span><a href="https://infosec.town/tags/monitoring" rel="nofollow noopener" target="_blank">#monitoring</a><span>? Things like "{sts/deploy} not progressing" or "crash-loop backoff". I've got alertmanager, but it has gaps.<br><br>(edit to say '44' since there are 40 people who want to kick it down the road until it becomes an emergency)</span></p>