When goflow is deployed as a Deployment+Service (as opposed to DaemonSet) and scale to more than one replica, it is likely to miss template definitions sent by OVS.

Collectors need IPFIX template definitions sent by OVS before being able to interpret flows. Because of load balancing, the goflow instance that receives the definitions might not be the one that later receives flows.

There can be several approaches to address this issue: sticky sessions (cons: if an OVS is stuck to a collector, it means collector cannot be scaled above than the number of OVS (nodes) (or extra instances would be unused); or finding a sharing mechanism so that all goflow instances share their definitions when received ; ...