Currently, Network Observability stores NetFlows locally which are not persistent. Instead, a persistent volume should be used by Loki to store NetFlows. In OCP, this is achieved with the PersistentVolumeClaims (PVC) object. By using this, it provides a consistent interface to the underlying storage without having to know the details. Here are items to consider for storage.

• Support for creating a PVC object
• Provide configuration options such as size of PVC, reclaim policy, etc.
• Support for different persistent volumes such as AWS EBS, Azure Disk/File, GCE persistent disk, Red Hat OpenShift Container Storage, vSphere VMDK, NFS, and Fibre Channel. Can Network Observability assume the provision of storage is already done?