The pod list was too long, and too cluttered. You needed only the name, the namespace, and the age. Kubectl can give you exactly that—if you know how to use column-level access.
Column-level access with kubectl means you control exactly which fields appear in your command output. It’s a practical way to filter signal from noise, especially when dealing with hundreds of resources. Instead of parsing verbose JSON or YAML, you define the columns you care about and output them cleanly.
The core tool is kubectl get with the --output option. Using -o custom-columns you can select object fields like .metadata.name or .status.phase in precise order. The syntax is straightforward but powerful:
kubectl get pods -o custom-columns=NAME:.metadata.name,NAMESPACE:.metadata.namespace,STATUS:.status.phase
This filters the output to three columns—no more, no less. Combined with --no-headers, the result becomes raw tabular data, perfect for scripts or pipelines.
For deeper visibility, you can use the jsonpath output format. This lets you query nested fields and arrays with granular control. Example: