Feature Request: UnmanagedContainerEvents alert type + Optional Auto-Kill

[nobodys-tools]

Problem

Current container lifecycle alerts cover only Komodo-managed workloads.
This leaves a blind spot for containers created outside Komodo (e.g., shell, cron, rogue Compose, compromised access).
I want an alert if a new container appears on a server that Komodo does not manage, so I can verify it’s intended.

Ask

Introduce a new AlertType (e.g., UnmanagedContainerEvents) that triggers on Docker runtime events even for containers not known to Komodo, covering:

• start
• stop
• restart
• create
• pull (image)

Filters & Noise Control

• Include/exclude by container name or image (glob/regex).
• Suppress Komodo-initiated actions (no alert if Komodo itself triggered the event).

Why this matters

• Detect unwanted/malicious containers quickly.
• Catch repeated restarts or suspicious creates/pulls.
• See when critical workloads stop — even if they weren’t deployed via Komodo.

Optional Auto-Kill Setting

• Server-level option: Auto-kill unmanaged containers
• When enabled:
  • Immediately stop and remove any container that triggers UnmanagedContainerEvents.
  • Log the action in Komodo’s activity log.
  • Send a "ContainerAutoKilled" alert for visibility.
• Configuration Options:
  • Whitelist containers by name, or image to prevent false positives.
• Purpose:
  • Security: Prevents unauthorized workloads from running.
  • Automation: Enforces Komodo-only container control without manual intervention.

[nobodys-tools]

If this is within scope and has potential to be merged, I’d be happy to implement it myself.

[mbecker20]

It sounds nice, would definitely appreciate a crack at it