fix: adjust "volume name" label for kube_persistentvolumeclaim_*

[multani]

What this PR does / why we need it:

This changes the name of the volume name label, reported by the kube_persistentvolumeclaim_* metrics, to be the same label as the one in the kube_persistentvolume_* metrics.

This makes it easier to combine the 2 related set of metrics together to being labels and values from one metric into another.

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)

Does not change cardinality

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 #2288

[k8s-ci-robot]

Welcome @multani!

It looks like this is your first PR to kubernetes/kube-state-metrics 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kube-state-metrics has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

[multani]

Sorry for the noise, I was trying to understand what was the problem with the commit message :facepalm:

Should be good now :)

[CatherineF-dev]

Also update https://github.com/kubernetes/kube-state-metrics/blob/main/CHANGELOG.md

Next:

[multani]

Also update https://github.com/kubernetes/kube-state-metrics/blob/main/CHANGELOG.md

Done! :+1:

[dgrisonnet]

/triage accepted /assign @CatherineF-dev @dgrisonnet

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: multani Once this PR has been reviewed and has the lgtm label, please ask for approval from dgrisonnet. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[mrueg]

Also update https://github.com/kubernetes/kube-state-metrics/blob/main/CHANGELOG.md

Next:

Has anything changed in the release process I'm not aware of? We usually do not update the changelog within the PR.

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[multani]

/remove-lifecycle stale

Still looking for feedback on how to move this forward (cf. https://github.com/kubernetes/kube-state-metrics/pull/2303#discussion_r1525927488)