Marko Mikulicic
Marko Mikulicic
What we need is a way to let the user create the Secret and only use it if it exists. This is a trick many operators leverage but I'd prefer...
Could you describe why running kubewatch into multiple clusters doesn't work for you?
kubewatch is part of the bitnami catalog; we're working on providing ARM images across the board and we'll get a multi-arch image for kubewatch for free. I'll post an update...
1.16 api has been merged (see #200) but not yet released.
Is as simple as just overriding the API endpoint url? (And otherwise uses the samrlnslack API?
hmm; turns out kubewatch is not using the new slack webhook API, but instead the old legacy client API, so it's not just a matter of exposing the base URL;...
soon I'm going to completely redesign the "handler" API; it's unnecessarily complicated and there is tons of code duplication; once that's done it will be easy to add other notification...
Helm chart repo is in https://github.com/bitnami/charts/tree/master/bitnami/kubewatch/
I don't know; can you run `kubectl get -o yaml` periodically and diff? perhaps kubewatch should be configurable in such a way that some common uninteresting update causes can be...
I think it's reasonable. However the pr drifted from master and we need help with rebasing it