Pod YAML

Learn the YAML structure for a Pod definition.

Pod YAML

Every Kubernetes object has four top-level fields: apiVersion, kind, metadata (name, labels) and spec (desired state). A pod's spec is a list of containers:

apiVersion: v1
kind: Pod
metadata:
  name: web
  labels:
    app: web
spec:
  containers:
    - name: nginx
      image: nginx:1.27
      ports:
        - containerPort: 80

containerPort is informational (like EXPOSE in a Dockerfile); it doesn't open traffic.

Command and arguments

A container's command can be changed in YAML: command replaces the image's ENTRYPOINT, and args its CMD:

spec:
  containers:
    - name: is
      image: busybox:1.36
      command: ["sh", "-c"]
      args: ["echo merhaba; sleep 3600"]

In YAML, lists are written either with square brackets (["a", "b"]) or with lines each starting with -.

Exercise Write a pod definition

Write a pod YAML: name web, label app: web; a single container named nginx, image nginx:1.27, containerPort: 80.

Show example solution

apiVersion: v1
kind: Pod
metadata:
  name: web
  labels:
    app: web
spec:
  containers:
    - name: nginx
      image: nginx:1.27
      ports:
        - containerPort: 80

Test yourself

What is the right apiVersion for a pod?
- batch/v1
- v1
- apps/v1
- pod/v1
Show answer

v1 — Pod, Service and ConfigMap are in the core group (v1); Deployment is in apps/v1.

Write the object's type.

apiVersion: v1
____: Pod

Show answer

apiVersion: v1
kind: Pod

Match the fields.

apiVersion

API group and version
kind

Object type
metadata

Name and labels
spec

Desired state

Next lesson: Creating a Pod

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies