Kubernetes Mistakes Side Effects

Kubernetes pod.yaml Practical Usage Guide

Kubernetes Pods are the fundamental building blocks of containerized applications, and the pod.yaml file is how we define and control them.

Here I’ve broken down the structure of a pod.yaml for a simplified understanding.

But simply writing a pod.yaml isn’t enough - understanding how to apply, modify, and optimize it can save you from unnecessary troubleshooting, resource wastage, and deployment issues.

Understand these pointers to get the most out of pod.yaml.

1. Applying and Managing pod.yaml

kubectl apply -f pod.yaml → Deploy a Pod

kubectl delete -f pod.yaml → Remove it

kubectl get pods, kubectl describe pod <pod-name> → Inspect

2. Editing and Updating a Running Pod

kubectl edit pod <pod-name> → Live editing (some changes require recreation)

kubectl apply -f pod.yaml → Updates only changed fields while preserving state

kubectl replace --force -f pod.yaml → Deletes and recreates the resource (disruptive)

3. Dry Run and Validate Before Deployment

kubectl apply --dry-run=client -f pod.yaml → Test changes without applying

kubectl apply --validate=true -f pod.yaml → Catch schema errors

4. Defining Resource Requests and Limits

Avoid OOMKills by setting:

resources:
  requests:
    cpu: "100m"
    memory: "256Mi"
  limits:
    cpu: "500m"
    memory: "512Mi"

5. Prevent unnecessary downtime by PodDisruptionBudget (PDB)

kind: PodDisruptionBudget
spec:
  minAvailable: 1

6. Using Liveness, Readiness, and Startup Probes

Auto restart failed Pods using:

livenessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10

Your pod.yaml isn’t just a static definition, it's a powerful tool.

Mastering it means less debugging, fewer outages, and smoother deployments.