Kubernetes Pod Creation: YAML Structure, Commands, and Example

This guide introduces the key fields of a Kubernetes resource definition: apiVersion (group and version), kind (resource type), metadata (basic data), spec (desired state), and status (current state).

Resources are created by submitting JSON to the API server; YAML files are accepted because the server automatically converts them to JSON before processing. Useful commands include kubectl api-versions to list API groups.

An example Pod manifest is provided:

apiVersion: v1
kind: Pod
metadata:
  name: pod-test
  namespace: default
  labels:
    app: myapp1
    tier: frontend
spec:
  containers:
  - name: myapp1
    image: ikubernetes/myapp:v1
    imagePullPolicy: IfNotPresent
    ports:
    - containerPort: 8090
      name: web
  - name: busybox
    image: busybox:latest
    command: ["/bin/sh", "-c", "sleep 10"]

To inspect the definition of container ports you can run kubectl explain pods.spec.containers.ports.

Pods can be created from the YAML file with kubectl create -f <filename>.yaml or applied with kubectl apply -f <filename>.yaml. Alternatively, you can use

kubectl run pod-run --image=ikubernetes/myapp:v1 --image-pull-policy=IfNotPresent --port=8090

to launch a Pod directly.

The article concludes with a list of related resources covering Kubernetes deployments, monitoring, scaling, high‑availability clusters, and Ansible automation.