Backporting #1938 to 2.3

[ryanrolds]

What this PR does / why we need it:

Backports #1938 to the 2.3 release branch. We are in process of updating our K8s cluster, but current OKRs require tracking these metrics sooner rather than later. Happy to backport to all release branches from 2.3 on.

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

It shouldn't affect it beyond what is already in the main branch.

[k8s-ci-robot]

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.

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-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ryanrolds
Once this PR has been reviewed and has the lgtm label, please assign dgrisonnet for approval by writing /assign @dgrisonnet in a comment. 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]

We consider new metrics a new feature and therefore would like to limit backporting to bug and security vulnerability fixes only.

[ryanrolds]

Makes sense. Thanks.