Why Every Software Tester Should Learn Kubernetes in 2026

# Which environments (namespaces) exist?
kubectl get namespaces

# What is running in the QA namespace?
kubectl get pods -n qa

# Example output
NAME                          READY   STATUS             RESTARTS   AGE
orders-api-7d9f8c6b5-abc12    1/1     Running            0          2h
payments-api-5c7d9b8f4-xyz9   0/1     CrashLoopBackOff   6          15m

# Avoid typing -n qa every time
kubectl config set-context --current --namespace=qa

# Confirm which namespace you are using
kubectl config view --minify | grep namespace

# Now this lists pods in qa
kubectl get pods

# Show deployments with their container images (version tags)
kubectl get deployments -o wide -n qa

# Just the image of one deployment
kubectl get deployment orders-api -n qa \
  -o jsonpath='{.spec.template.spec.containers[0].image}'

# -> registry.example.com/orders-api:v2.4.1

# When did it last roll out?
kubectl rollout history deployment/orders-api -n qa

# Last 100 log lines from a pod
kubectl logs orders-api-7d9f8c6b5-abc12 -n qa --tail=100

# Follow logs live while you run a test
kubectl logs -f deployment/orders-api -n qa

# Logs from the previous (crashed) container
kubectl logs payments-api-5c7d9b8f4-xyz9 -n qa --previous

# Only lines mentioning an order ID
kubectl logs deployment/orders-api -n qa | grep "ORD-10492"

kubectl describe pod payments-api-5c7d9b8f4-xyz9 -n qa

# Scroll to the Events section at the bottom, e.g.:
# Warning  Failed     Failed to pull image "payments-api:v2.5": not found
# Warning  BackOff    Back-off restarting failed container

# Recent events in the whole namespace, newest last
kubectl get events -n qa --sort-by=.lastTimestamp | tail -20

# Which config values does the app get? (ConfigMaps hold non-secret settings)
kubectl get configmaps -n qa
kubectl describe configmap orders-config -n qa

# Environment variables inside a running pod
kubectl exec -n qa orders-api-7d9f8c6b5-abc12 -- printenv | grep -i url

# Note: never copy Secret values into bug reports or chats

TEST ENVIRONMENT HEALTH CHECK (run before testing)

Namespace: ______   Date/time: __________

[ ] kubectl get pods  -> all Running, READY full
[ ] RESTARTS low and not increasing
[ ] kubectl get deploy -o wide -> expected image tags
      orders-api   : v_____
      payments-api : v_____
[ ] No recent Warning events (kubectl get events)
[ ] Smoke test passed

Result: Ready / Blocked (reason: ____________)

BUG REPORT — with environment evidence

Title      : Checkout returns 500 when coupon applied
Environment: qa namespace, orders-api image v2.4.1
Steps      : 1. ... 2. ... 3. ...
Expected   : Order total shows discounted price
Actual     : HTTP 500, error page
Evidence   :
  - Log excerpt (kubectl logs ... | grep ORD-10492):
    NullPointerException at CouponService.apply(...)
  - Screenshot attached
Pod status : Running, 0 restarts (not an env issue)

KUBECTL CHEAT SHEET FOR TESTERS

kubectl get pods -n <ns>                     # health
kubectl get deploy -o wide -n <ns>           # versions
kubectl logs <pod> -n <ns> --tail=100        # recent logs
kubectl logs -f deploy/<name> -n <ns>        # live logs
kubectl logs <pod> -n <ns> --previous        # crashed container
kubectl describe pod <pod> -n <ns>           # events
kubectl get events -n <ns> --sort-by=.lastTimestamp
kubectl get svc,endpoints -n <ns>            # routing