Deployment status and history in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What command shows the current status of a Kubernetes deployment?

Use kubectl rollout status deployment/<deployment-name> to see the current status of a deployment.

beginner

How can you view the history of revisions for a Kubernetes deployment?

Use kubectl rollout history deployment/<deployment-name> to list all past revisions of the deployment.

beginner

What does the command kubectl rollout undo deployment/<deployment-name> do?

It rolls back the deployment to the previous revision, undoing the last change.

intermediate

What information does kubectl rollout history provide about each revision?

It shows the revision number and the change cause if annotated, helping track what changed in each deployment update.

beginner

Why is monitoring deployment status important in Kubernetes?

It helps ensure your application updates are successful and lets you quickly detect and fix problems during rollout.

Which command shows the rollout status of a deployment named 'webapp'?

A kubectl rollout status deployment/webapp

B kubectl get pods webapp

C kubectl describe deployment webapp

D kubectl rollout history deployment/webapp

The command kubectl rollout status deployment/webapp shows the current rollout status.

How do you see all past revisions of a deployment?

A kubectl rollout history deployment/<name>

B kubectl get deployment --history

C kubectl describe deployment --revisions

D kubectl rollout status deployment/<name>

Use kubectl rollout history deployment/<name> to view deployment revisions.

What happens when you run kubectl rollout undo deployment/myapp?

A It shows the deployment status

B It deletes the deployment

C It updates the deployment to the latest image

D It rolls back to the previous deployment revision

The command rolls back the deployment to the previous revision.

Which command helps you track what changed in each deployment revision?

A kubectl logs deployment/<name>

B kubectl rollout history deployment/<name>

C kubectl get pods

D kubectl describe pod

The rollout history command shows revision details and change causes.

Why should you monitor deployment status during updates?

A To increase cluster size

B To delete old pods

C To ensure updates succeed and catch errors early

D To change container images manually

Monitoring helps confirm successful updates and detect problems quickly.

Explain how to check the status and history of a Kubernetes deployment and why it matters.

Think about commands to see current state and past changes, plus why watching updates is useful.

Describe the steps to rollback a Kubernetes deployment to a previous version.

Recall commands for history, undo, and status checking.