vmware-archive/kubewatch

Not able to get notifications for all other resources except pods and services

Opened this issue · 2 comments

Hi, I have deployed kubewatch and given a cluster-admin role to the service account used in the deployment.
Also connected it with slack.
I am only able to receive notifications for pods, services, namespaces and deployments, though I have enabled all other resources as shown below:
image
And in the logs getting only success messages, no other error logs for other resources.
image
Also the slack channel shows only pods, services, namespaces and deployments alerts:
image
image

Can anyone please guide if I am missing any configuration? or where should I look for the errors for other resources?

Hi @mkmik can you help me with this?

The error log shows:
==> Writing config file...
time="2020-10-30T08:19:31Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-deployment
time="2020-10-30T08:19:31Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-service
time="2020-10-30T08:19:31Z" level=info msg="Processing add to namespace: default" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing add to namespace: kube-node-lease" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing add to namespace: kube-public" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing add to service: kube-system/kube-dns" pkg=kubewatch-service
time="2020-10-30T08:19:31Z" level=info msg="Processing add to service: default/kubernetes" pkg=kubewatch-service
time="2020-10-30T08:19:31Z" level=info msg="Processing add to service: kube-system/metrics-server" pkg=kubewatch-service
time="2020-10-30T08:19:31Z" level=info msg="Processing add to namespace: kube-system" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing add to namespace: monitoring" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing add to deployment: kube-system/metrics-server" pkg=kubewatch-deployment
time="2020-10-30T08:19:31Z" level=info msg="Processing add to deployment: kube-system/coredns" pkg=kubewatch-deployment
time="2020-10-30T08:19:31Z" level=info msg="Processing add to pod: default/kubewatch" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Processing add to pod: kube-system/metrics-server-5df78f85b-zwhpd" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Processing add to pod: kube-system/coredns-86f9b748-8xjrx" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Processing add to pod: kube-system/coredns-86f9b748-lvjr5" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Processing add to pod: kube-system/coredns-86f9b748-zmg9t" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Kubewatch controller synced and ready" pkg=kubewatch-deployment
time="2020-10-30T08:19:31Z" level=info msg="Kubewatch controller synced and ready" pkg=kubewatch-pod
time="2020-10-30T08:19:31Z" level=info msg="Kubewatch controller synced and ready" pkg=kubewatch-service
time="2020-10-30T08:19:31Z" level=info msg="Kubewatch controller synced and ready" pkg=kubewatch-namespace
time="2020-10-30T08:19:31Z" level=info msg="Processing update to pod: default/kubewatch" pkg=kubewatch-pod

It is only able to start controller for four resources.
@snebel29 @mkmik @arjan