Inventory

inventory

inventory is the fastest orientation command in HarrierOps Kube.

Use it when you need to understand what kind of Kubernetes environment you landed in before you choose the next deeper command.

What This Command Answers

• How broad does the visible cluster slice look?
• Does the environment look managed, self-managed, or only weakly classifiable?
• Are exposure, risky workloads, or identity sprawl already obvious?
• Which command is most likely to pay off next?

Run It

harrierops-kube inventory --output table

If you want a saved structured artifact:

harrierops-kube inventory --output json --outdir ./harrierops-kube-demo

Example Table Output

visibility scope	environment type	public paths	privileged workloads	high-impact service accounts	next commands
broad cluster slice	self-managed-like	3	1	2	exposure, workloads, service-accounts, rbac

When To Use It

• right after whoami
• before opening a specific service surface at random
• when you need a fast shape check instead of deeper object review

What To Look For

• whether visibility looks broad, narrow, or partial
• exposure counts such as ingresses, load balancers, and node ports
• risky workload counts such as privileged or host-touching workloads
• identity footprint such as service-account and grant density
• the built-in next-command routing hints

Why It Matters

Good prioritization starts with knowing what kind of place this is.

A cluster with exposed paths, risky workloads, and dense identity signals should feel different from a quiet namespace-scoped application view. inventory gives you that shape early so you do not waste time opening the wrong lane first.

What Should Stand Out First

• the visibility assessment
• exposure footprint
• risky workload footprint
• identity footprint
• the next command recommendations

If You See..., Go Next To...

• If you see a strong ingress, load balancer, or node-port footprint, go next to Exposure because the cluster edge deserves review first.
• If you see privileged or host-touching workload cues, go next to Workloads because the next question is which running thing matters most.
• If you see dense service-account or grant signals, go next to Service Accounts and RBAC because the next question is how identity and access are distributed.

What To Do Next

• Treat inventory as a routing command, not the end of the investigation.
• Follow the strongest visible lane first instead of trying to read every command equally.
• Use it to decide whether your next stop should be exposure, workloads, service-accounts, or rbac.

Boundary

inventory is an orientation command.

It should show cluster shape clearly enough to drive prioritization. It is not deep RBAC analysis, workload-by-workload triage, or full reachability proof.