Deployment status and history in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Check the rollout status of a deployment

You run the command kubectl rollout status deployment/myapp. What output indicates the deployment has successfully rolled out?

A deployment "myapp" successfully rolled out

B Error from server (NotFound): deployments.apps "myapp" not found

C deployment "myapp" failed to rollout

D Waiting for deployment "myapp" rollout to finish: 1 out of 3 new replicas have been updated...

💡 Hint

Look for a message confirming success, not errors or partial updates.

The command kubectl rollout status deployment/myapp shows the current rollout status. The message deployment "myapp" successfully rolled out means the deployment finished updating all pods successfully.

🧠 Conceptual

intermediate

Understanding deployment revision history

What does the command kubectl rollout history deployment/myapp show?

A A list of all revisions of the deployment with change causes

B The YAML manifest of the deployment

C The status of all pods in the deployment

D The current pod logs for the deployment

💡 Hint

Think about what 'history' means in this context.

The kubectl rollout history command lists all previous revisions of a deployment, showing when and why changes were made.

❓ Troubleshoot

advanced

Diagnosing a stuck deployment rollout

You notice a deployment rollout is stuck and not progressing. Which command helps you see detailed rollout status including pod conditions?

A kubectl get pods --all-namespaces

B kubectl describe deployment myapp

C kubectl logs deployment/myapp

D kubectl rollout undo deployment/myapp

💡 Hint

You want detailed info about the deployment and its pods.

kubectl describe deployment myapp shows detailed info including events and pod status that help diagnose rollout issues.

🔀 Workflow

advanced

Rollback a deployment to a previous revision

You want to rollback the deployment myapp to revision 2. Which command correctly performs this rollback?

A kubectl revert deployment/myapp --revision 2

B kubectl rollback deployment myapp --revision=2

C kubectl undo deployment myapp revision 2

D kubectl rollout undo deployment/myapp --to-revision=2

💡 Hint

Check the exact syntax for rollback with revision number.

The correct syntax to rollback to a specific revision is kubectl rollout undo deployment/myapp --to-revision=2.

✅ Best Practice

expert

Best practice for monitoring deployment history in production

Which approach is best to keep track of deployment history and changes in a Kubernetes production environment?

A Manually save deployment YAML files on local machines after each change

B Rely only on <code>kubectl get pods</code> to check running pods after deployment

C Use <code>kubectl rollout history</code> combined with GitOps to track deployment manifests and changes

D Use <code>kubectl logs</code> of pods to track deployment changes

💡 Hint

Think about combining Kubernetes tools with version control for best tracking.

Combining kubectl rollout history with GitOps practices ensures deployment changes are tracked both in Kubernetes and version control, enabling audit and rollback.