Turbo storing historical resource data for clusters and namespaces that are no longer present.

I would like to propose an enhancement to Turbonomic around the retention and visibility of historical resource data for Kubernetes clusters and namespaces that have been deleted or are no longer present in the cluster.

In customer environments, it is common for namespaces to be created and removed as part of application lifecycle management, testing activities, or temporary project deployments. Once these namespaces are removed, the associated resource consumption and utilisation history can become difficult or impossible to review. This can create challenges when customers need to investigate previous capacity issues, perform trend analysis, validate chargeback/showback reports, or support post-incident reviews.

The idea would be for Turbonomic to retain historical performance and resource utilisation data for a configurable period after a namespace has been deleted, allowing users to continue viewing and reporting on that information even though the namespace no longer exists in the live environment. Ideally, this historical data would remain searchable and available through reporting, dashboards, and analysis views, while being clearly identified as belonging to a deleted namespace.

This capability could provide significant value for customers who need longer-term visibility into application behaviour, resource consumption patterns, and infrastructure planning activities, particularly in highly dynamic Kubernetes environments where namespaces are frequently created and removed.