Given the connectivity requirements,
most nfacctd instances are currently deployed outside Kubernetes. The goal is
to ensure that nfacctd can be deployed and scaled within a Kubernetes
environment.
In public cloud environments, BGP and flowlogs traffic are typically tunneled
to the VPC through a VPN, Direct connect etc. nfacctd instances are deployed
either on-premises or within the VPC, and are manually managed outside of
Kubernetes.
Similarly:
