It would be useful to enrich the NetFlow data by including the cluster id, along with some information such as the region.  This would be the start in managing multiple clusters.  As a reference, on the command line, you can get the cluster id from the ClusterVersion object with:

oc get clusterversion -o jsonpath='{.items[].spec.clusterID}{"\n"}'

Some cluster metadata is accessible in nodes annotations, e.g:

    node.kubernetes.io/instance-type: m6i.xlarge
    topology.kubernetes.io/region: eu-west-3
    topology.kubernetes.io/zone: eu-west-3b

FLP can read this information on k8s-enrich stage setup.

Adding this information should be optional (saving space for users not interested in multi-cluster)

Some scenarios:

1. Have data stored in the same persistent volume for more than one cluster.

2. Have the flow collector receive NetFlows from one or more clusters which will then store this data in the same persistent volume.

The goal is to provide enough data so when a user wants to see this data, it can resolve the missing data.