Practice scaling a deployment and forcing pod recreation safely.
Understand how replica count changes affect running workloads in Kubernetes.
Review current deployment and pod counts before making changes.
Command
kubectl get podsExpected Result
You should see the current pods associated with the deployment.
Increase the replica count to run more pod instances.
Command
kubectl scale deployment <deployment-name> --replicas=3Expected Result
Kubernetes should begin creating additional pods.
Confirm that the new pods came up successfully.
Command
kubectl get podsExpected Result
You should see more pod instances than before.
Remove a pod manually to observe self-healing behavior.
Command
kubectl delete pod <pod-name>Expected Result
The pod should terminate and a replacement should appear if managed by the deployment.
Confirm that the workload stabilizes after scaling and recreation.
Command
kubectl rollout status deployment/<deployment-name>Expected Result
You should see successful rollout or stabilization feedback.
You understand how scaling affects replicas and pod lifecycle.
You can explain Kubernetes self-healing behavior for deployment-managed pods.