As a follow-up on NETOBSERV-37, goflow-kube should expose its status wrt. IPFIX collection started.
In particular, it should tell whether it is receiving flows AND is able to interpret them / having also received the corresponding template definitions.
Other statuses might be interesting to consider, such as:

• started listening flows
• started receiving flows
• started receiving flows and being able to understand them

This could be implemented via a standardized "health" endpoint (e.g. could be inspired from microprofile spec https://download.eclipse.org/microprofile/microprofile-health-2.1/microprofile-health-spec.html#_appendix_a_rest_interfaces_specifications )

Consider also the case where the state is currently OK and goes degraded (e.g. flows not recognized anymore because they reference an unknown definition), with some kind of tolerance (there could be both recognized and unrecognized flows, => maybe goflow could expose, as part of its health, some kind of ratio like "75% of flows received in the last 5 minutes are OK")