Add quota management information and recommendations - including reductions

Thank you for submitting your idea. We truly value our relationship with our customers and appreciate your engagement.

After a thorough review and consideration of various factors, we have decided to mark this idea as Not Under Consideration at this time.

Currently, Turbonomic does not generate recommendations to reduce namespace quotas, and this is by design. It’s important to understand that resource quotas act as upper limits rather than indicators of actual usage. Unlike container resource allocations, a high namespace quota does not necessarily imply wasted physical resources, it simply defines a cap.

For example, a namespace might be using only 10% of its quota today, but that usage could spike to 100% tomorrow due to application scaling or new pod deployments. Determining how much a quota can be safely reduced and how much historical data would be needed to support that decision is not straightforward.

Additionally, Turbonomic treats quotas as part of allocation-based capacity planning. Many customers intentionally set higher quotas to reserve capacity for future growth or peak demand. Automatically recommending quota reductions would require Turbonomic to estimate how much headroom to retain, which varies significantly across customers and workloads. This introduces risk, as overly aggressive downsizing could block necessary rightsizing actions due to quota constraints.

Instead, Turbonomic focuses on optimizing the workloads themselves, using quotas as boundaries rather than targets. We believe quota management is best left to customers, once workload optimization is complete.

As an alternative approach, we suggest customers consider setting lower initial quotas and leveraging Turbonomic’s recommendations to increase them as needed.

We hope you can help the customer understand the value Turbonomic provides through its robust optimization capabilities.