CatherineF-dev
CatherineF-dev
Yes, could you list all CRs for this CRD (storage.k8s.io)? Guess there are two CRs.
One solution is to add log verbose level to these spam logs. Do you know which line is generating these spam logs? You might can find it from error logs.
This error is from https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go#L535. However, hard to configure log level for client-go package. If [contextual logging](https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/3077-contextual-logging/README.md ) is used in [client-go](https://github.com/kubernetes/client-go), it can be possible. Example PR on using...
It has a panic error inside pull-custom-metrics-apiserver-test ``` --- FAIL: TestApplyTo (1.71s) --- FAIL: TestApplyTo/only-secure-port (1.71s) panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error:...
/lgtm /hold Feel free to unhold. Not sure whether it waits other PRs or not.
In asking an approval for this PR. I only have LGTM permission so far.
@dgrisonnet need review again.
This PR is not needed due to https://github.com/kubernetes/kube-state-metrics/pull/2388
Could you provide steps to reproduce this issue?