Granular and Extended Event Alerting #3
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixes vmware-archive#105 This feature adds support to alert on specific event type per resource. For example, to watch only create and update events on deployment resource, kubewatch.yaml should be resource: deployment: watch: true events: create: true update: true delete: false This also adds custom event type 'loadbalancercreate' to notify when there is a loadbalancer created for a service. resource: services: watch: true events: create: true update: true delete: true loadbalancercreate: true
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes vmware-archive#105
This feature adds support to alert on specific event type per resource.
For example, to watch only create and update events on deployment resource, kubewatch.yaml should be
resource:
deployment:
watch: true
events:
create: true
update: true
delete: false
This also adds custom event type 'loadbalancercreate' to notify when there is a loadbalancer created for a service.
resource:
services:
watch: true
events:
create: true
update: true
delete: true
loadbalancercreate: true