oc Adm Top Examples¶

Introduction¶

Node commands show cluster capacity, readiness, labels, and resource usage. They are useful when pods are Pending, nodes are NotReady, or workloads are concentrated on one node.

When You Need This Command¶

Use this command when you need to inspect, change, or verify OpenShift resources from the terminal without relying on the web console.

Syntax¶

oc <command> <resource> [name] -n <project>

Practical Examples¶

oc get nodes

oc get nodes -o wide

oc adm top nodes

oc describe node worker-1

Example output:

NAME       STATUS   ROLES    AGE   VERSION
master-0   Ready    master   20d   v1.28.9
worker-1   Ready    worker   20d   v1.28.9

Verification¶

oc get events -n app --sort-by=.lastTimestamp

oc get pods -n app -o wide

Common Mistakes¶

• Looking only at the final error and ignoring events.
• Checking the wrong project with oc.
• Changing several objects at once before confirming the current state.

Production Notes¶

Run read-only commands first, check the active project, and prefer declarative manifests for repeatable changes.

Quick Checklist¶

• Confirm the active project.
• Inspect the exact object named in the error.
• Read recent events.
• Apply one focused fix.
• Verify status after the change.

Related Guides¶

• oc Commands Cheat Sheet
• oc Auth Can I Examples
• oc Get Events Examples

Summary¶

oc Adm Top Examples is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.