usually that is due to traffic from a node that do...
# neuvector-security
q
usually that is due to traffic from a node that doesn’t have an enforcer running. sometimes it is control plane nodes with a taint so the daemonset does not schedule there. other times it can be due to a cni or service mesh issue, if they have tunnels or other interfaces that neuvector is not aware of