Automated cherry pick of #45031

[crassirostris]

Cherry pick of #45031 on release-1.6.

#45031: Remove too verbose label from fluentd metrics

[k8s-reviewable]

This change is 

[k8s-github-robot]

The 'parent' PR of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement. (release-note-experimental must be explicit for cherry-picks)

[piosz]

/lgtm
/approve

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crassirostris, piosz

Needs approval from an approver in each of these OWNERS Files:

• cluster/addons/fluentd-gcp/OWNERS [crassirostris,piosz]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

[crassirostris]

@k8s-bot node e2e test this

[crassirostris]

@k8s-bot node e2e test this

[crassirostris]

Well I don't know what's wrong with this test, but it's certainly not this PR's fault

@fejta FYI

[fejta]

Well the job is definitely failing (and consistently to boot) so I don't see anything for me to do.

Node suite is node team and namespace issues are api machinery. Contact them if you think the results are wrong? (Dawn or Daniel)

[crassirostris]

It's passed in the original PR: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/45031/pull-kubernetes-node-e2e/27384/

@dchen1107 @lavalamp Have you seen this issue? Are those just flakes?

[dchen1107]

I quickly looked into all failures in #45068, #45121 and #45083, and the all volume related tests failed because volume cannot be gc properly, thus pod cannot be deleted.

I believe we hit a known issue: #43534 which is triggered by bumping to go1.8 (#41636)

[MrHohn]

@ixdy Here is the node e2e failure

[dchen1107]

Checked build.log with more detail:

W0428 03:59:39.616] Run: ('docker', 'pull', 'gcr.io/k8s-testimages/kubekins-node:1.7-latest')
I0428 03:59:39.989] 1.7-latest: Pulling from k8s-testimages/kubekins-node
I0428 03:59:39.990] Digest: sha256:b3cc9993ddfb862bc7c7075f7cbd37fdbefbf3096df3a94ff2da4c2957517d2c
I0428 03:59:39.990] Status: Image is up to date for gcr.io/k8s-testimages/kubekins-node:1.7-latest

kubekins-node:1.7-latest was introduced through PR: https://github.com/kubernetes/test-infra/pull/2521/files

This proves the theory I had at #45083 (comment)

[ixdy]

oops, small bug, easy fix in kubernetes/test-infra#2624.

[ixdy]

@k8s-bot node e2e test this

[crassirostris]

@dchen1107 @ixdy Thanks a lot!

[k8s-github-robot]

Automatic merge from submit-queue

[k8s-cherrypick-bot]

Commit found in the "release-1.6" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.