Salut la Product Team,

I am writing to request an enhancement to the EKS Lens reporting feature within the [Your Cloud Management Platform Name].
I have noticed (and I am not the only one) that in the cost reports generated by EKS Lens, there are instances where costs are labeled as "N/A," particularly in relation to the "EC2-Other" category.
This label is not very convenient for understanding the allocation of costs and can lead to confusion when analysing customers' cloud expenditure.

Issue Encountered:
In the Navigator EKS cost reports, it is frequently encountered that a label "N/A" which seems to be associated with costs that cannot be directly attributed to a specific resource or tag. This makes it challenging to fully understand and manage our cloud costs, as we (TAMs, CREs, Customers) cannot easily identify the source or reason for these unallocated expenses.

Feature Request - what is expected:
I would like to request the following features to be considered for implementation in EKS Lens:
- Enhanced labelling mechanism: An improved system for labelling resources that currently fall under the "N/A" category. This could include automated suggestions for labelling based on resource type, usage patterns, or other identifiable characteristics.

• Customisable label mapping: it would be very useful to be able to define custom label mappings for costs that are not directly attributable to a specific resource or tag. This would allow our customers to categorise and allocate these costs according to their internal accounting practices.

• Detailed unallocated cost breakdown: A dedicated section or report within EKS Lens that provides a detailed breakdown of unallocated costs, including possible reasons for why they are not labeled and suggestions for how to address this.

• Labelling policy enforcement: Tools or checks within EKS Lens to ensure that all resources within EKS clusters are labelled according to our organisation's policies, with alerts for any resources that are missing required labels.

• then we need to teach them how to fish by providing some documentation and best practices for labelling within EKS Lens, including how to handle common scenarios that result in "N/A" labels and strategies for improving cost allocation accuracy.

Impact:
Implementing these features would greatly enhance our customers' ability to track and manage cloud costs with precision. It would also provide clarity for their finance and operations teams, enabling them to make more informed decisions based on accurate cost allocation data.

Conclusion:
I believe that these enhancements would be beneficial not only to many other users of EKS Lens who are seeking to optimise their cloud cost management practices.

Merci :)