UPSTREAM: 59170: Fix kubelet PVC stale metrics

[jsafrane]

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1542135

[jsafrane]

/assign @derekwaynecarr

[jsafrane]

/retest

[jsafrane]

/retest

[jsafrane]

/retest

[childsb]

/approve

[mfojtik]

/approve

@smarterclayton I think this will have to cherry-pick to release-3.9 right? and we should hold till the branch cut is complete?

[jsafrane]

/cherrypick release-3.9

If the PR lands after the release is cut, ensure developers apply /cherrypick release-3.9 comment to ensure a new PR is opened against origin/release-3.9.

let's see how this works...

[openshift-cherrypick-robot]

@jsafrane: once the present PR merges, I will cherry-pick it on top of release-3.9 in a new PR and assign it to you.

In response to this:

/cherrypick release-3.9

If the PR lands after the release is cut, ensure developers apply /cherrypick release-3.9 comment to ensure a new PR is opened against origin/release-3.9.

let's see how this works...

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.

[tsmetana]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: childsb, jsafrane, mfojtik, tsmetana

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

The pull request process is described here

Needs approval from an approver in each of these files:

• vendor/k8s.io/kubernetes/pkg/kubelet/OWNERS [mfojtik]

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

[jsafrane]

/retest

[jsafrane]

/retest

[jsafrane]

/test extended_conformance_install
/test unit
/test extended_networking_minimal
/test gcp

[jsafrane]

/retest

[jsafrane]

/retest

[openshift-merge-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[openshift-merge-robot]

Automatic merge from submit-queue (batch tested with PRs 18745, 18637).

[openshift-cherrypick-robot]

@jsafrane: new pull request created: #18787

In response to this:

/cherrypick release-3.9

If the PR lands after the release is cut, ensure developers apply /cherrypick release-3.9 comment to ensure a new PR is opened against origin/release-3.9.

let's see how this works...

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.

[openshift-ci-robot]

@jsafrane: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/gcp	eba5a49	link	/test gcp

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.