Suggestion: Merge NameSpace labels into the labels list about opencost HOT 7 CLOSED

I vote we make progress on #27 and then address this. Let me know if anyone feels differently.

from opencost.

Thanks for sharing this idea, Luis! This sounds useful to me. Is there a particular scenario or two that you have in mind? I'm just trying to better understand when a namespace_label and namespace_name wouldn't have a 1-to-1 relationship.

from opencost.

We label our namespaces with stuff like team, owner, cost centre, etc... Some times a team or a cost centre has multiple namespaces and it would be nice to have a aggregated view on those.

from opencost.

This is helpful. And I agree that this would be nice to include. To confirm, you use kubernetes labels and not annotations for this?

There would be a possibility of a label conflict, e.g. owner label applied to namespace with a different owner applied at the pod-level. Maybe we should respect the most granular option (e.g. pod in this case). Any thoughts?

from opencost.

Yes, labels, not annotations. I think that in the case of a conflict, the pod label should prevail as it is more specific.

from opencost.

I agree that this would be useful. Let's send it back on the cost model API as a separate field so we don't lose the provenance of the label on the frontend. Merging/conflicts can be handled by the user of the API (and in the Kubecost product).

from opencost.

@luisdavim this data should now be available in latest as namespaceLabels! Does this support what you're looking to do?!

from opencost.