OCPBUGS-114874: Document filtering oc adm top pod metrics by node

[Pratik-Redhat-Tech]

Fixes OCPBUGS-114874

Document how to list pod CPU/memory usage on a specific node using the existing --field-selector flag:

oc adm top pod -A --field-selector spec.nodeName=<node_name>

This is not a new --node flag. Upstream kubernetes/kubernetes#141581 added --node and was closed because --field-selector spec.nodeName=... already covers that workflow (kubernetes/kubernetes#139107). This PR only adds the missing example so the existing flag is discoverable.

Signed-off-by: Pratik Langde plangde@redhat.com

Made with Cursor

[openshift-ci-robot]

@Pratik-Redhat-Tech: This pull request references Jira Issue OCPBUGS-114874, which is invalid:

• expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes OCPBUGS-114874

Document how to list pod CPU/memory usage on a specific node using the existing --field-selector flag:

oc adm top pod -A --field-selector spec.nodeName=<node_name>

This is not a new --node flag. Upstream kubernetes/kubernetes#141581 added --node and was closed because --field-selector spec.nodeName=... already covers that workflow (kubernetes/kubernetes#139107). This PR only adds the missing example so the existing flag is discoverable.

Signed-off-by: Pratik Langde plangde@redhat.com

Made with Cursor

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @Pratik-Redhat-Tech. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[Pratik-Redhat-Tech]

/jira refresh

[openshift-ci-robot]

@Pratik-Redhat-Tech: This pull request references Jira Issue OCPBUGS-114874, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.