Typorithm · easy

Pod Manifest

pod-manifestkubernetespodmanifestcontainers

Saved on this device

Full lesson · 8 learning steps Open any exercise for focused practice

Step 1 of 8 · intro card

Learn Pod Manifest

Workloads

A Pod manifest is the smallest deployable unit: apiVersion v1, kind Pod, a metadata.name, and a spec.containers list naming each image and its ports.

A Pod is the smallest schedulable object in Kubernetes — one or more containers that share a network and lifecycle.

Every manifest carries four keys: apiVersion and kind identify the object, metadata names it, and spec describes the desired state.

Inside spec.containers each entry needs a name and an image; containerPort documents the port the app listens on.

apiVersion: v1, kind: Pod identify the object.

metadata.name must be unique in the namespace.

spec.containers lists name, image, and ports.

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

Connect each part of the code to the concept before you type.

Core objects like Pod live in the v1 (legacy core) API group, written as apiVersion: v1.

apiVersion: v1

kind names the object type the manifest describes — here a single Pod.

kind: Pod

metadata.name uniquely identifies the Pod within its namespace.

metadata:
  name: web

spec.containers lists each container by name and image.

- name: web
      image: nginx:1.27

containerPort documents which port the container listens on.

containerPort: 80

Read the concept map and follow the code breakdown.

Type the implementation, repair mistakes and work through every recall exercise.

Use the final check without hints; revisit weak concepts in short practice sessions.