Build a Practical Delivery and Troubleshooting Example in Kubernetes Fundamentals

Define the build target

For Delivery and Troubleshooting, deploy a new image tag, observe rollout status, deliberately use an invalid image tag, diagnose ImagePullBackOff, then restore the last healthy Deployment revision. Build the boundary case using this implementation lens: Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics.

Keep the Delivery and Troubleshooting build centered on these technical constraints: Use declarative manifests and kubectl apply so the desired state is reviewable. Watch kubectl rollout status deployment/NAME after a Deployment change. Apply them through this path lens: Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics. Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics.

Implement the core behavior

Implement Delivery and Troubleshooting around the module artifact—a Deployment update with recorded rollout, diagnosis, and rollback steps—and keep the implementation specific to this path context: Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
spec:
  replicas: 2
  selector:
    matchLabels: {app: web}
  template:
    metadata:
      labels: {app: web}
    spec:
      containers:
        - name: web
          image: nginx:1.27
          readinessProbe:
            httpGet: {path: /, port: 80}
            initialDelaySeconds: 2
            periodSeconds: 5

kubectl apply -f deployment.yaml && kubectl rollout status deployment/web

The Deployment reaches its desired replicas; diagnostics identify a failing rollout or the rollback restores a healthy revision.

practice/\n├── README.md\n├── delivery-and-troubleshooting-build.yaml\n└── evidence/\n    └── expected-result.txt

Run the complete path

Run one realistic Delivery and Troubleshooting case end to end and record the required evidence: rollout status, Pod events/logs, and confirmation that the restored revision is healthy. Interpret the result through this path context: Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics.

Change one meaningful condition

Modify one condition central to Delivery and Troubleshooting using this path context: Use Kubernetes API objects, Pods, controllers, Services, ConfigMaps/Secrets, volumes, probes, scheduling, RBAC, rollouts, events, and kubectl diagnostics. Predict the new result before rerunning the same workflow.

Verify the artifact

Your deliverable is a Deployment update with recorded rollout, diagnosis, and rollback steps.

Common mistakes to avoid

• Run kubectl get pods to identify unhealthy Pods and states.
• Use kubectl describe pod POD to inspect events and probe or scheduling failures.
• Use kubectl logs POD and kubectl logs POD --previous when a container restarts.
• Use kubectl rollout history and kubectl rollout undo deployment/NAME when a Deployment revision must be reverted.