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

Configurable resource types to be watched #43

Closed
ngtuna opened this issue Sep 30, 2016 · 4 comments
Closed

Configurable resource types to be watched #43

ngtuna opened this issue Sep 30, 2016 · 4 comments
Assignees

Comments

@ngtuna
Copy link
Contributor

ngtuna commented Sep 30, 2016

No description provided.

@ngtuna
Copy link
Contributor Author

ngtuna commented Oct 19, 2016

I consider keep this issue open although #45 getting merged already. Somehow we should think more on supported options for resources to be watched. At this moment, it's running like this:

// rc, po and svc would be watched
$ kubewatch config resource --rc --po --svc

// only svc would be watched
$ kubewatch config resource --svc

By default, supported changes are: create, delete, update. We can always think about configurations more specific like I only want to watch added services, or deleted pod, or updated rc.

@tylerauerbeck
Copy link
Contributor

@ngtuna Not sure where this stands. If you could point me in the right direction I'd be more than happy to work on this.

@tylerauerbeck
Copy link
Contributor

Part two of this issue (granular event alerting) is now being worked as part of #105

@arunkumarmurugesan
Copy link

arunkumarmurugesan commented Oct 25, 2018

I'm also looking for similar kind of granular event alerting. Also, want to understand why its keep sending "update" notification into slack channel even there is no action performed in the cluster.

FYI:
kubewatch
A service in namespace kube-system has been updated:

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

No branches or pull requests

3 participants