Stop Typing Full Kubernetes Resource Names: Use kubectl Short Names

Bobby W

3 min read

·

Sep 24, 2026

--

Listen

Share

Press enter or click to view image in full size

Learn what po, svc, and deploy mean—and how kubectl api-resources reveals what your cluster actually supports.

When beginners first use Kubernetes, commands can feel unnecessarily long:

kubectl get deployments

But the same command can usually be written as:

kubectl get deploy

deploy is a Kubernetes resource short name. It is not a custom shell alias; it is discovered from the Kubernetes API.

Common short names

Here are several you will see often:

Press enter or click to view image in full size

You can use a short name with more than get:

kubectl describe po api-7d8f9c
kubectl delete deploy old-api
kubectl logs po/api-7d8f9c

Do not memorize everything

Ask the cluster:

kubectl api-resources

This command prints the resource types supported by the API server available to your current context. Its output includes columns such as:

• NAME: the resource name used by the API
• SHORTNAMES: available abbreviations
• APIVERSION: the API group and version
• NAMESPACED: whether the resource belongs to a namespace
• KIND: the object kind used in YAML

That last distinction helps beginners: the resource name is usually plural and lowercase — deployments—while the YAML kind is singular and capitalized—Deployment.

Useful ways to filter the output

Show only namespace-scoped resources:

kubectl api-resources --namespaced=true

Show cluster-scoped resources:

kubectl api-resources --namespaced=false

Show resources that support a particular verb:

kubectl api-resources --verbs=list

Filter by API group:

kubectl api-resources --api-group=apps

Print just the resource names for scripting:

kubectl api-resources -o name

You can also search the displayed table:

kubectl api-resources | grep -i deploy

Why the command is better than a static cheat sheet

Clusters are not all identical. Operators and platforms can install Custom Resource Definitions, or CRDs, which add new resource types. A CRD may define its own short names — or none at all.

That means a short name found online might not exist in your cluster, while your cluster may have additional ones that a generic list does not show.

kubectl api-resources gives you the answer for the cluster you are connected to right now.

One practical warning

Before running a destructive command, prefer the full resource name if an abbreviation feels unclear:

kubectl delete deployment old-api

Short names save typing. Full names can improve readability in documentation, shared scripts, and incident runbooks.

The command to remember

You do not need to memorize every Kubernetes resource:

kubectl api-resources

Use short names interactively for speed, and use the discovery command whenever you are unsure.

If you want more practical commands for diagnosing Pods and workloads, I created a free field guide you can keep beside your terminal:

Download the Kubernetes Troubleshooting Free Kit