Resource Types and Kinds
What You'll Learn
You'll discover how Kubernetes organizes its API objects through resource types and their associated Kinds, forming the foundation of cluster interaction.
Understanding Resources and Kinds
In Kubernetes, every object you create—whether a Pod, Service, or ConfigMap—is defined by two related concepts: its resource type and its Kind.
Think of it like a library catalog system: the resource type is the URL path you use to access items (like /books or /magazines), while the Kind is the formal classification appearing on the item itself (like "Book" or "Magazine" on the cover).
Resource Types
A resource type is the API endpoint name used in URLs and commands. It's typically lowercase and plural:
podsservicesdeploymentsconfigmaps
When you run kubectl get pods, you're querying the pods resource type.
Kinds
A Kind is the object schema name—the formal type identifier in the API. It appears in YAML manifests and is typically singular and capitalized:
PodServiceDeploymentConfigMap
In your manifest files, the kind: field specifies this value.
The Relationship
Every API resource type maps to a Kind. When you POST a manifest with kind: Pod to the API server, it routes to the pods resource endpoint. This separation allows the API to maintain RESTful conventions (plural URLs) while keeping object definitions clear (singular kinds).
The API server uses this mapping internally to validate, store, and retrieve objects correctly through etcd.
Key Takeaway: Resource types are plural API endpoints for accessing objects, while Kinds are singular schema names that define object structure—they're two views of the same concept, bridging REST conventions with object-oriented design.