Pranshu Srivastava

icon indicating a website link rexablog.netlify.app icon indicating an email [email protected]

icon company @RedHatOfficial icon location India icon location SIG Instrumentation Co-chair @kubernetes | Emeritus @nodejs

Results 524 comments of Pranshu Srivastava

Address lint reports

I think it'll pick up on the changes automatically once [the gocyclo issues](https://goreportcard.com/report/github.com/kubernetes/kube-state-metrics#gocyclo) are addressed. There's also a "refresh now" button there on the same link if you want to...

Address lint reports

/assign @glokta1

Address lint reports

/assign @venkatbvc

Address lint reports

ACK, taking a look.

Address lint reports

I wonder with the recent dicussions and directions that have come to light, specifically around migrating the CRS featureset, is this something that might be affected?

Can't watch custom resources with the same kind but different API groups

ACK! /assign @rexagod

kube_pod_annotations reports incorrect nodes (all metrics for the same node)

@vyakovlev-hw Maybe I'm missing something but, I'm not sure how you're able to see the `node` label in `kube_pod_annotations`, since we are [not exposing any as of v2.5.0](https://github.com/kubernetes/kube-state-metrics/blob/v2.5.0/internal/store/pod.go#L977) or even...

Truncating values of kube-state-metrics when trying to get different units

I've been digging around the logic for the metric values, and I'm positive that we are not _rounding_ anything. However, I was half-expecting to see `float64` values being `Sprintf`-ed by...

Truncating values of kube-state-metrics when trying to get different units

Not sure that'll work if the underlying handler code is explicity setting the `float64` value to `%v`-like representation.

Truncating values of kube-state-metrics when trying to get different units

I'll look a bit more into this and report back.