Feature Overview (aka. Goal Summary)  Preserve site-specific information when storing data collected as part of the Network Observability Operator.

Goals (aka. expected user outcomes)

Multi-cluster enablement of Network Observability requires inclusion of information that describes the cluster from which is was obtained. For example, enrichment of the NetFlow data by including the cluster id, region and availability zone.

Representative data examples include:

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

Example scenarios:

• Have data stored in the same persistent volume for more than one cluster.
• Have the flow collector receive NetFlows from one or more clusters which will then store this data in the same persistent volume.

Requirements (aka. Acceptance Criteria):

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

Use Cases (Optional):

• As a developer of a network application that is run on multiple clusters, I'd like to concentrate the network observability data into a single pane of glass without losing cluster-specific data.
   

  Questions to Answer (Optional):

Out of Scope

*

Background

* 

Customer Considerations

• Some customers use Splunk as the data aggregator.
• Some customers want to incorporate non-Kubernetes cluster data.

Documentation Considerations

Interoperability Considerations