WIP: do not query for node name from api for metrics resource

[haircommander]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 46aef8e|WIP: do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[haircommander]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt 4

[openshift-ci]

@haircommander: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/34e20ca0-7174-11f0-844a-dd96e8b37473-0

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 257247a|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• 85ed8ee|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 257247a|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• 666efbb|UPSTREAM: : unset KubeletSeparateDiskGC: does not specify an upstream backport in the commit message
• 85ed8ee|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[haircommander]

/retest

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 750fa27|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• b7534f3|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 750fa27|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• b7534f3|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• b90b2d1|stats: handful of optimizations: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 8246eb4|UPSTREAM: 132983: cleanup: fetch individual PodResourceInfo from allocated resource state: the upstream PR kubernetes/kubernetes#132983 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0ee4ca0|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• 2225618|UPSTREAM: : stats: handful of optimizations: does not specify an upstream backport in the commit message
• 9570feb|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[haircommander]

/payload-job periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

[openshift-ci]

@haircommander: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3bdc52f0-7943-11f0-81b3-d4ce7b481974-0

[haircommander]

/payload-job periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

[openshift-ci]

@haircommander: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a041d630-794c-11f0-930e-b89352640fc5-0

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 8246eb4|UPSTREAM: 132983: cleanup: fetch individual PodResourceInfo from allocated resource state: the upstream PR kubernetes/kubernetes#132983 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 9570feb|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• b91a38f|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• e6e12c1|UPSTREAM: : stats: handful of optimizations: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[haircommander]

/payload-job periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

[openshift-ci]

@haircommander: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.20-nightly-x86-payload-control-plane-6nodes

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6f397860-794f-11f0-8044-9efb1b9469a0-0

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 8246eb4|UPSTREAM: 132983: cleanup: fetch individual PodResourceInfo from allocated resource state: the upstream PR kubernetes/kubernetes#132983 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0d70dca|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• d4a1057|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• f4b4f91|UPSTREAM: : stats: handful of optimizations: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 8246eb4|UPSTREAM: 132983: cleanup: fetch individual PodResourceInfo from allocated resource state: the upstream PR kubernetes/kubernetes#132983 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 0d70dca|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• 488b0ea|WIP: UPSTREAM: : don't report metrics for host network pods: does not specify an upstream backport in the commit message
• d4a1057|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• f4b4f91|UPSTREAM: : stats: handful of optimizations: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: haircommander
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the 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:

• DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 0d70dca|UPSTREAM: : WIP do not query for node name from api for metrics resource: does not specify an upstream backport in the commit message
• 5681732|WIP: UPSTREAM: : don't report metrics for host network pods: does not specify an upstream backport in the commit message
• d4a1057|UPSTREAM: : add http logging for kubelet metrics endpoint: does not specify an upstream backport in the commit message
• f4b4f91|UPSTREAM: : stats: handful of optimizations: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[haircommander]

/test e2e-aws-ovn-runc
/test e2e-aws-ovn-cgroupsv2

[haircommander]

/retest

[haircommander]

/test e2e-aws-ovn-crun

[haircommander]

/retest

[openshift-ci]

@haircommander: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-disruptive	85ed8ee	link	false	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-dualstack	85ed8ee	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-openstack-csi-manila	85ed8ee	link	false	/test e2e-openstack-csi-manila
ci/prow/e2e-openstack-csi-cinder	85ed8ee	link	false	/test e2e-openstack-csi-cinder
ci/prow/e2e-aws	85ed8ee	link	false	/test e2e-aws
ci/prow/k8s-e2e-gcp-five-control-plane-replicas	85ed8ee	link	false	/test k8s-e2e-gcp-five-control-plane-replicas
ci/prow/e2e-metal-ipi-ovn-ipv6	b7534f3	link	false	/test e2e-metal-ipi-ovn-ipv6
ci/prow/k8s-e2e-gcp-ovn	5681732	link	true	/test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-ovn-serial	5681732	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-techpreview	5681732	link	false	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-crun-wasm	5681732	link	true	/test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-crun	5681732	link	true	/test e2e-aws-ovn-crun
ci/prow/verify	5681732	link	true	/test verify
ci/prow/e2e-aws-ovn-cgroupsv2	5681732	link	true	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-fips	5681732	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-gcp	5681732	link	true	/test e2e-gcp
ci/prow/unit	5681732	link	true	/test unit
ci/prow/e2e-aws-ovn-runc	5681732	link	true	/test e2e-aws-ovn-runc

Full PR test history. Your PR dashboard.

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