Kubernetes object
A record stored in the cluster that describes one thing you want, such as a Pod, a Service or a Namespace.
In more detail
Creating an object is not a command that runs once; it is a record of intent that controllers keep acting on. Every object has four top-level keys: apiVersion, kind, metadata and spec, and most gain a status written by the cluster. You create, read, change and delete objects through the API server, usually with kubectl.
Related terms
- apiVersion — The manifest field that names which API group and version defines an object, such as v1 or apps/v1.
- object kind — The manifest field that says what type of object a file describes, such as Pod, Deployment or Service.
- spec and status — The two halves of most Kubernetes objects: spec is what you ask for, and status is what the cluster reports is actually true.
- Kubernetes manifest — A YAML or JSON file that describes one or more Kubernetes objects, ready to be sent to the cluster with kubectl apply.
- API server — The Kubernetes control plane component that serves the Kubernetes API; every read and change to the cluster goes through it.
Taught in
- Persistent And Ephemeral Volumes — Certified Kubernetes Application Developer (CKAD) Exam Prep
- From Docker To Desired State — Kubernetes: Production-Grade Container Orchestration
- Namespaces, Labels And Declarative Manifests — Kubernetes: Production-Grade Container Orchestration
- StorageClasses, CSI And Dynamic Provisioning — Kubernetes: Production-Grade Container Orchestration
- Package The Service As A Helm Chart — Kubernetes: Production-Grade Container Orchestration