Christian Schlotter

Alternative approaches to the current `subsystem` field: Current example, results in metric `capi_cluster_` instead of `capi_cluster_x_k8s_io_v1beta1_cluster_`: ```yaml kind: CustomResourceStateMetrics spec: resources: - groupVersionKind: group: cluster.x-k8s.io kind: Cluster version: v1beta1 namespace:...

> One thing I am still not following, if we have a GVK, why do we need a subsystem/apiversion as well? Isn't this information already contained in the GVK? The...

I agree, so the idea would be to have a field `metricNamePrefix ` and remove `subsystem` as well as `namespace`. * If `metricNamePrefix ` is not set, it calculates the...

/hold Want to do some more testing tomorrow :-)

> On the prefix/name: Every metric ksm exposes used `kube_`, does it make sense to prefix everything with kube_crd_ by default? I would prefer to at least not enforce it....

Changed the defaulting to `kube_` now, do we have consensus on that topic? If no, should we move the namespace/subsystem/metricsNamePrefix discussion to a new/separate issue? Also did some tests and...

> Can you update https://github.com/kubernetes/kube-state-metrics/blob/master/docs/customresourcestate-metrics.md as well? Yes sure 👍 thanks for pointing me to it 😃

I also updated the docs now. Happy to get another round of feedback :-) Thanks to everyone involved 👍

Hi, is there already some work going on? Otherwise I would like to help here :-) Christian Schlotter , Daimler TSS GmbH, Imprint

@jtopjian would it be an extension at `openstack/loadbalancer/v2/extensions/quotas` analog to the neutron ones or simply `openstack/loadbalancer/v2/quotas`? https://github.com/gophercloud/gophercloud/tree/master/openstack/networking/v2/extensions/quotas I've already got some working code here to workaround the missing library functions...