Skip to content

feat: add webhook filtering by failure category and severity#37

Open
yieon-lyon wants to merge 1 commit intoaws-samples:mainfrom
yieon-lyon:feat/webhook-category-severity-filter
Open

feat: add webhook filtering by failure category and severity#37
yieon-lyon wants to merge 1 commit intoaws-samples:mainfrom
yieon-lyon:feat/webhook-category-severity-filter

Conversation

@yieon-lyon
Copy link
Copy Markdown

Introduce two new optional config options to control which failures trigger webhook calls:

  • WEBHOOK_SKIP_CATEGORIES: comma-separated list of detection layers to skip (e.g. PodPhase,PodCondition)
  • WEBHOOK_MIN_SEVERITY: minimum severity threshold (LOW | MEDIUM | HIGH | CRITICAL)

Both filters apply as AND logic. Unset values preserve existing behavior. Skipped webhooks are logged with category and severity.

Affected files: config/config.go, controller/pod_controller.go, examples/04-configmap.yaml

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Introduce two new optional config options to control which failures
trigger webhook calls:

- WEBHOOK_SKIP_CATEGORIES: comma-separated list of detection layers
  to skip (e.g. PodPhase,PodCondition)
- WEBHOOK_MIN_SEVERITY: minimum severity threshold
  (LOW | MEDIUM | HIGH | CRITICAL)

Both filters apply as AND logic. Unset values preserve existing
behavior. Skipped webhooks are logged with category and severity.

Affected files: config/config.go, controller/pod_controller.go,
examples/04-configmap.yaml

Signed-off-by: Lyon <yieon1230@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant