Goflow2 has some issues like a coupled integration with Kube-Enricher, resulting in a code that is difficult to maintain. It also performs multiple and duplicate internal data conversions that could impact performance.

This task consists on:

1. Create Benchmarks
2. Replace Goflow2 by VMWare's go-ip library. There is already a running PoC here: https://github.com/netobserv/goflow2-kube-enricher/pull/25
3. Compare New Benchmarks with the others
4. Evaluate performance, stability, and code maintainability to decide whether is worth replacing it

If we decide to finally replace Goflow2 by VMWare's go-ip library, we should create a new Jira issue to make sure all these changes are ready for production, e.g. make sure that the output data is the same in both cases and we don't add any regression.