fix k8s events DCR filter bug #1577
Merged
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.
This pull request updates the event filtering logic in the
in_kube_events.rbplugin to improve how Kubernetes events are processed. The main change is to pass the involved object's name to the exclusion filter, which enables more precise filtering of events by resource name in addition to namespace.Event filtering improvements:
parse_and_emit_recordsmethod now passes the involved object's name (involvedObjectName) as a parameter toKubernetesApiClient.isExcludeResourceItem, allowing exclusion checks to consider both the resource name and namespace.