You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In my cluster I'm having issues with the high cardinality of cAdvisor metrics and trying to make an allowlist of only the metrics krr needs. The readme mentioned these metrics
I noticed however that there were others missing like machine_memory_bytes and machine_cpu_cores that the cluster summary asks for and are otherwise missing.
For kube-state-metrics there's a few others I noticed but might have missed, because I haven't yet tried limiting kube-state-metrics because its cardinality was not as high as cAdvisor was.
This might not even be all of them, I didn't search very deeply in the code yet.
Expected behavior
A list of all metrics that krr expects so I can make a thorough allowlist. Possibly tailored to which component of kube-prometheus-stack each comes from (cAdvisor, kubelet, kube-state-metrics, etc), though not strictly necessary.
The text was updated successfully, but these errors were encountered:
Describe the bug
In my cluster I'm having issues with the high cardinality of cAdvisor metrics and trying to make an allowlist of only the metrics krr needs. The readme mentioned these metrics
I noticed however that there were others missing like
machine_memory_bytes
andmachine_cpu_cores
that the cluster summary asks for and are otherwise missing.For kube-state-metrics there's a few others I noticed but might have missed, because I haven't yet tried limiting kube-state-metrics because its cardinality was not as high as cAdvisor was.
This might not even be all of them, I didn't search very deeply in the code yet.
Expected behavior
A list of all metrics that krr expects so I can make a thorough allowlist. Possibly tailored to which component of kube-prometheus-stack each comes from (cAdvisor, kubelet, kube-state-metrics, etc), though not strictly necessary.
The text was updated successfully, but these errors were encountered: