Can Falcon KAC be deployed in watcher mode only?

[r3motecontrol]

We are migrating from KPA to Falcon KAC for Kubernetes visibility. We already have an admission controller and are primarily interested in visibility only. Can the falcon-watcher component be run independently without requiring the falcon-ac and falcon-client?

I modified the chart to only start the falcon-watcher container. However, the container failed to start (Unix socket errors).

Container logs

E0130 20:02:37.229554    159] "ipc: Failed to connect to unix socket" "error"="dial unix /var/private/kac-watcher.sock: connect: no such file or directory" "address"="/var/private/kac-watcher.sock"
E0130 20:02:38.230227    159] "ipc: Failed to connect to unix socket" "error"="dial unix /var/private/kac-watcher.sock: connect: no such file or directory" "address"="/var/private/kac-watcher.sock"
E0130 20:02:39.230954    159] "ipc: Failed to connect to unix socket" "error"="dial unix /var/private/kac-watcher.sock: connect: no such file or directory" "address"="/var/private/kac-watcher.sock"

Startup probe failed: Get "http://10.244.0.8:4080/startz": dial tcp 10.244.0.8:4080: connect: connection refused

I am unsure if I missed something obvious (or) whether these components are so tightly coupled that it's impossible to exclude others.