Why production readiness matters in Kubernetes - See It in Action

Why Production Readiness Matters in Kubernetes

📖 Scenario: You are working as a DevOps engineer for a company that runs a web application on Kubernetes. Your team wants to make sure the application is ready to run smoothly in the real world, where many users will access it at the same time. This means the application must be production ready.Production readiness means the app can handle real traffic, recover from problems, and keep running without interruptions.

🎯 Goal: Learn why production readiness matters and how to check basic readiness in Kubernetes using a simple readinessProbe. You will create a Kubernetes pod configuration that includes a readiness check to make sure the app is ready before it receives traffic.

📋 What You'll Learn

Create a Kubernetes pod manifest with a container named webapp

Add a readinessProbe to check the app's health using an HTTP GET request

Set the readiness probe to check the path /health on port 8080

Print the pod manifest YAML to verify the readiness probe is included

💡 Why This Matters

🌍 Real World

In real companies, production readiness ensures apps stay available and reliable for users. Kubernetes readiness probes help manage app traffic safely.

💼 Career

DevOps engineers and SREs use readiness probes daily to keep cloud apps healthy and avoid downtime.

1

Create a basic Kubernetes pod manifest

Create a YAML manifest for a Kubernetes pod named webapp-pod with a container named webapp using the image nginx:latest. Include the container port 8080.

Kubernetes

# Write the YAML manifest for the pod named webapp-pod
# with container webapp using image nginx:latest and port 8080

Hint

Use apiVersion: v1, kind: Pod, and define metadata.name as webapp-pod. Under spec.containers, add one container with the name webapp, image nginx:latest, and port 8080.

2

Add a readiness probe configuration

Add a readinessProbe to the webapp container. Configure it to perform an HTTP GET request to path /health on port 8080.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: webapp-pod
spec:
  containers:
  - name: webapp
    image: nginx:latest
    ports:
    - containerPort: 8080
    # Add readinessProbe here

Hint

Under the container webapp, add readinessProbe with httpGet specifying path: /health and port: 8080.

3

Explain why readiness probes matter

Add a comment in the YAML explaining that the readiness probe helps Kubernetes know when the app is ready to receive traffic.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: webapp-pod
spec:
  containers:
  - name: webapp
    image: nginx:latest
    ports:
    - containerPort: 8080
    readinessProbe:
      httpGet:
        path: /health
        port: 8080
# Add a comment explaining readiness probe purpose

Hint

Add a comment starting with # below the readinessProbe explaining its purpose in simple words.

4

Print the final pod manifest

Print the complete YAML manifest for the pod named webapp-pod including the readiness probe.

Kubernetes

# Print the YAML manifest

Hint

Use a print statement to output the full YAML manifest as a string exactly as written.

Practice

1. Why is production readiness important in Kubernetes deployments?

easy

A. It ensures the application runs reliably and recovers from failures.

B. It makes the application run faster on local machines.

C. It reduces the size of container images.

D. It allows skipping testing before deployment.

Solution

1. Step 1: Understand production readiness purpose

   Production readiness means preparing your app to handle real-world use, including failures and load.

2. Step 2: Identify key benefits

   Ensuring reliability and recovery from failures keeps the app stable for users.

3. Final Answer:

   It ensures the application runs reliably and recovers from failures. -> Option A

4. Quick Check:

   Production readiness = reliability and recovery [OK]

Hint: Focus on stability and failure recovery for production readiness [OK]

Common Mistakes:

• Confusing production readiness with performance optimization
• Thinking it only affects local development
• Assuming it removes the need for testing

2. Which Kubernetes feature helps check if your app is running correctly in production?

easy

A. ConfigMap

B. Persistent Volume

C. Namespace

D. Liveness Probe

Solution

1. Step 1: Identify health check features in Kubernetes

   Kubernetes uses probes to check app health: liveness and readiness probes.

2. Step 2: Match feature to checking if app is running

   Liveness probe checks if the app is alive and restarts it if not.

3. Final Answer:

   Liveness Probe -> Option D

4. Quick Check:

   Liveness Probe = app health check [OK]

Hint: Liveness probe checks if app is alive, readiness probe checks if ready [OK]

Common Mistakes:

• Confusing ConfigMap with health checks
• Thinking Namespace controls app health
• Assuming Persistent Volume monitors app status

3. Given this Kubernetes pod spec snippet, what happens if the container crashes?

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

medium

A. Nothing happens; the container keeps running.

B. The pod is deleted permanently.

C. Kubernetes restarts the container after failing the health check.

D. Kubernetes scales the pod to zero replicas.

Solution

1. Step 1: Understand liveness probe behavior

   Liveness probe checks container health and triggers restart if it fails.

2. Step 2: Apply to container crash scenario

   If container crashes, health check fails, so Kubernetes restarts it automatically.

3. Final Answer:

   Kubernetes restarts the container after failing the health check. -> Option C

4. Quick Check:

   Liveness failure = container restart [OK]

Hint: Liveness probe failure triggers container restart [OK]

Common Mistakes:

• Thinking pod is deleted permanently on failure
• Assuming container keeps running despite crash
• Confusing scaling with health check actions

4. You deployed a pod with resource limits but it keeps getting killed. What is the likely cause?

medium

A. The pod has no liveness probe defined.

B. The pod exceeded its memory limit and was terminated by Kubernetes.

C. The pod is missing a readiness probe.

D. The pod's image is too large.

Solution

1. Step 1: Understand resource limits effect

   Kubernetes kills pods that exceed their memory limits to protect node stability.

2. Step 2: Link pod termination to resource limits

   If pod is killed repeatedly, likely it uses more memory than allowed.

3. Final Answer:

   The pod exceeded its memory limit and was terminated by Kubernetes. -> Option B

4. Quick Check:

   Memory limit exceeded = pod killed [OK]

Hint: Check pod memory usage against limits if it keeps restarting [OK]

Common Mistakes:

• Assuming missing probes cause pod kills
• Blaming image size for pod termination
• Confusing readiness and liveness probes with resource limits

5. You want to make your Kubernetes app production-ready by ensuring it recovers quickly from failures and does not overload the cluster. Which combination should you configure?

hard

A. Set liveness and readiness probes, and define resource requests and limits.

B. Only set resource limits without probes.

C. Use ConfigMaps to store environment variables and skip probes.

D. Deploy without resource limits but add multiple replicas.

Solution

1. Step 1: Identify production readiness needs

   Recovery from failures requires health checks; avoiding overload needs resource limits.

2. Step 2: Match Kubernetes features to needs

   Liveness and readiness probes help detect and recover from failures; resource requests and limits control cluster usage.

3. Final Answer:

   Set liveness and readiness probes, and define resource requests and limits. -> Option A

4. Quick Check:

   Probes + resource limits = production readiness [OK]

Hint: Combine probes with resource limits for stable production apps [OK]

Common Mistakes:

• Skipping probes and relying only on resource limits
• Using ConfigMaps instead of health checks
• Ignoring resource limits and risking cluster overload