Getting Started with Kubernetes: A DevOps Engineer's Practical Guide

Why Kubernetes?

If you're managing containerized applications at any meaningful scale, Kubernetes (K8s) is essential. It handles scheduling, self-healing, scaling, and service discovery — so you can focus on delivering features rather than babysitting servers.

Core Concepts

Pods

The smallest deployable unit in Kubernetes. A Pod encapsulates one or more containers sharing storage and network.

apiVersion: v1
kind: Pod
metadata:
  name: nginx-pod
spec:
  containers:
  - name: nginx
    image: nginx:1.25
    ports:
    - containerPort: 80

Deployments

Deployments manage replica sets and enable rolling updates with zero downtime.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-app
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
      - name: web
        image: myapp:v1.2.0
        resources:
          requests:
            cpu: "100m"
            memory: "128Mi"
          limits:
            cpu: "500m"
            memory: "256Mi"

Services

Services provide stable networking endpoints for your Pods, abstracting away individual Pod IPs.

apiVersion: v1
kind: Service
metadata:
  name: web-service
spec:
  selector:
    app: web
  ports:
  - port: 80
    targetPort: 8080
  type: ClusterIP

Practical Tips

1. Always set resource limits — prevents noisy neighbor issues
2. Use liveness and readiness probes — enables self-healing and safe rolling updates
3. Store secrets in Kubernetes Secrets — never hardcode credentials in images
4. Use namespaces — logical isolation for environments within the same cluster

Next Steps

Once comfortable with basics, explore Helm for package management, HPA for autoscaling, and Ingress controllers for traffic routing.