Assume a company, where there is a common k8s cluster, which is used by several people and each of them has their own namespace.
Now, they should be able to create persistent volumes (PV). There are tools to monitor costs per namespace like kubecost, but PVs are a global resource not bound to namespaces, yet incurring costs. Of course, we could use PersistentVolumeClaims (PVC) here, but in some cases, PVs are unused, so that might cause a problem.
Is there a sensible way to assign costs of PVs to namespaces?
Leave an answer