Skip to content
This repository has been archived by the owner on Apr 8, 2022. It is now read-only.

Ignoring certain messages #273

Open
ghost opened this issue Jun 30, 2021 · 4 comments
Open

Ignoring certain messages #273

ghost opened this issue Jun 30, 2021 · 4 comments

Comments

@ghost
Copy link

ghost commented Jun 30, 2021

Lets say I only care about when a node is deleted or created, how do I prevent kubewatch from constantly flooding with updated messages?

@ashtonian
Copy link

similar use case - we are on eks and they recycle the kube proxy (provided by aws plugin) at least once an hour.

@tonholis
Copy link

tonholis commented Oct 7, 2021

+1

@m0sh1x2
Copy link

m0sh1x2 commented Nov 3, 2021

I am using docker.io/bitnami/kubewatch:0.1.0-debian-10-r429" and it is constantly flooding with update messages.

@aantn
Copy link

aantn commented Jan 8, 2022

If this is still relevant for anyone, I wrote an open source project on top of Kubewatch (see here) which lets you apply filters in yaml. E.g. you can write:

triggers:
- on_deployment_update: {}
actions:
- resource_babysitter:
     fields_to_monitor: ["spec"]
     omitted_fields: [
        "status",
        "metadata.generation",
        "metadata.resourceVersion",
        "metadata.managedFields",
     ]

Or you could only track node creations:

triggers:
- on_node_create: {}
actions:
- resource_babysitter: {}

Happy to add features if anyone needs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants