Closed ovidiutirla closed 5 months ago
This issue is currently awaiting triage.
If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
This verb can be used only in 'fmt.Errorf' calls (%w) which makes the CI to fail on the main branch, see ci-go-lint, ci-benchmark-tests, ci-e2e-tests.
/assign @rexagod
The ci-benchmark-tests
is failing as it's using the code from the main branch. Looks like for some reason on https://github.com/kubernetes/kube-state-metrics/pull/2358 the CI didn't ran.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mrueg, ovidiutirla
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Merging this manually to get CI working :)
That's my bad, I didn't notice the log.Fatalf
call and assumed that to be a fmt.Errorf
for some reason (%w
is only valid there). 🤦
What this PR does / why we need it: The %w makes the CI to fail, replacing it back to %s. After the https://github.com/kubernetes/kube-state-metrics/pull/2358 was merged, looks like the CI is failing on the main branch.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality) no impact
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #