Disabling "Event" resources does not work

[petrov-e]

Hi, the option to ignore "Event" resources doesn't seem to work.

I tried to specify in the configuration similarly to other modules:

resourcesToWatch:
  event: false

or

resourcesToWatch:
  events: false

This does not help, I see in the logs that the corresponding module starts despite the configuration:

time="2023-01-27T10:09:55Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-Event

On our large cluster, this gives a lot of noise in notifications to Slack. Thank you in advance!

[arikalon1]

Hi @petrov-e
Thanks for reporting it

What is the chart version you're using?
(You can easily see it with helm list)

[petrov-e]

@arikalon1

version: 3.3.6

[arikalon1]

Thanks.
I think there's a bug in that chart version.
Can you please try it with version 3.3.5?

Just add to the helm install command --version 3.3.5

Can you update if you see the same issue on 3.3.5?

[petrov-e]

There is no such problem in 3.3.5 version of the chart, since a different version of the image is used: docker.io/bitnami/kubewatch:0.1.0-debian-10-r571. There is no kubewatch-Event controller in this version.

But in this version there is a bug described here: #20

"Missing" namespace. It looks like this:

[arikalon1]

Thanks for the update @petrov-e
We're looking into it

[RoiGlinik]

@petrov-e you are right that functionality is missing ( to disable events resources ) We will add it to the next version.
We just released 3.3.7 with a fix to the name space image you have added

[backaf]

Just deployed kubewatch in a development cluster and started to see the same issue. My events are related to the max dns search list:

Search Line limits were exceeded, some search paths have been omitted, the applied search line is: monitoring.svc.cluster.local svc.cluster.local cluster.local my.corp.com your.corp.com our.corp.com

This isn't easy to fix on our side since the max dns search is a current limitation. There is a feature gate available in 1.23 but it's in alpha:

https://v1-23.docs.kubernetes.io/docs/concepts/services-networking/dns-pod-service/
https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/

Certain events are definitely helpful, it would perhaps be better to exclude certain events from the notifications?

[arikalon1]

Thanks for reporting it @backaf

Would you be willing to contribute a PR for that enhancement? (adding exclusion filters to kubewatch)

Alternatively, if you're only interested in k8s warning events, if can you send the via Robusta, you could do the filtering there.

[backaf]

I'm definitely not experienced enough for such a PR, otherwise it would have sounded like a nice challenge :)

Currently I'm hitting the Teams webhook rate limits so I won't be able to use kubewatch in our clusters. I will take a look at Robusta, I didn't know about it! Thanks!