Rollback to previous version in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to rollback the deployment named 'webapp' to the previous revision.

Kubernetes

kubectl rollout undo deployment/[1]

Drag options to blanks, or click blank then click option'

Adatabase

Bfrontend

Cbackend

Dwebapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong deployment name.

Forgetting to specify 'deployment/' before the name.

The command kubectl rollout undo deployment/webapp rolls back the 'webapp' deployment to its previous version.

2fill in blank

medium

Complete the command to rollback the deployment 'api-server' to revision 2.

Kubernetes

kubectl rollout undo deployment/api-server --to-revision=[1]

Drag options to blanks, or click blank then click option'

A2

B1

C3

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' instead of a revision number.

Using a revision number that does not exist.

Using --to-revision=2 rolls back the deployment to revision 2.

3fill in blank

hard

Fix the error in the command to rollback the deployment 'frontend' to the previous revision.

Kubernetes

kubectl rollout undo [1] frontend

Drag options to blanks, or click blank then click option'

Areplicaset

Bdeployment

Cservice

Dpod

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pod' or 'service' instead of 'deployment'.

Omitting the resource type.

The correct resource type to rollback is deployment. Pods, services, and replicasets cannot be rolled back this way.

4fill in blank

hard

Fill both blanks to rollback the deployment 'backend' to revision 3 and watch the rollout status.

Kubernetes

kubectl rollout undo deployment/[1] --to-revision=[2] && kubectl rollout status deployment/backend

Drag options to blanks, or click blank then click option'

Abackend

Bfrontend

C3

D2

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong deployment name or revision number.

Forgetting to watch rollout status after rollback.

The command rolls back the 'backend' deployment to revision 3 and then watches its rollout status.

5fill in blank

hard

Fill all three blanks to rollback the deployment 'api' to revision 1, then check rollout history.

Kubernetes

kubectl rollout undo deployment/[1] --to-revision=[2] && kubectl rollout history deployment/[3]

Drag options to blanks, or click blank then click option'

Aapi

B1

Capi-server

Dbackend

Attempts:

3 left

💡 Hint

Common Mistakes

Using different deployment names in rollback and history commands.

Using invalid revision numbers.

This command rolls back the 'api' deployment to revision 1 and then shows its rollout history.

Practice

1. What does the command kubectl rollout undo deployment/myapp do in Kubernetes?

easy

A. It updates the deployment 'myapp' to the latest image version.

B. It rolls back the deployment 'myapp' to its previous version.

C. It deletes the deployment 'myapp' permanently.

D. It scales the deployment 'myapp' to zero replicas.

Solution

1. Step 1: Understand the command purpose

   The command kubectl rollout undo is used to revert a deployment to a previous state.

2. Step 2: Apply to the given deployment

   Using deployment/myapp specifies which deployment to rollback.

3. Final Answer:

   It rolls back the deployment 'myapp' to its previous version. -> Option B

4. Quick Check:

   Rollback command = revert deployment [OK]

Hint: Rollback uses 'kubectl rollout undo' with deployment name [OK]

Common Mistakes:

• Confusing rollback with delete command
• Thinking it updates to latest version instead of previous
• Using scale command instead of rollback

2. Which of the following is the correct syntax to rollback a deployment named 'webapp' to its previous version?

easy

A. kubectl rollout undo deployment/webapp

B. kubectl rollback deployment/webapp

C. kubectl undo deployment webapp

D. kubectl rollback undo webapp

Solution

1. Step 1: Recall correct rollback syntax

   The correct command to rollback is kubectl rollout undo deployment/<name>.

2. Step 2: Match syntax with deployment name

   Replacing <name> with 'webapp' gives kubectl rollout undo deployment/webapp.

3. Final Answer:

   kubectl rollout undo deployment/webapp -> Option A

4. Quick Check:

   Correct rollback syntax = rollout undo [OK]

Hint: Remember 'rollout undo' is the rollback command [OK]

Common Mistakes:

• Using 'rollback' instead of 'rollout undo'
• Incorrect order of words in command
• Missing 'deployment/' prefix

3. Given the following commands executed in order:

kubectl apply -f deployment-v1.yaml
kubectl apply -f deployment-v2.yaml
kubectl rollout undo deployment/myapp

What will be the current version of the deployment 'myapp' after the last command?

medium

A. Version 1 (deployment-v1.yaml)

B. Version 2 (deployment-v2.yaml)

C. No change, still version 2

D. Deployment deleted

Solution

1. Step 1: Understand deployment updates

   First, version 1 is applied, then version 2 updates the deployment.

2. Step 2: Rollback command effect

   The rollback command reverts the deployment to the previous version, which is version 1.

3. Final Answer:

   Version 1 (deployment-v1.yaml) -> Option A

4. Quick Check:

   Rollback reverts to last version before update [OK]

Hint: Rollback returns to version before last update [OK]

Common Mistakes:

• Assuming rollback deletes deployment
• Thinking rollback keeps current version
• Confusing rollback with reapply

4. You tried to rollback a deployment using kubectl rollout undo deployment/myapp but got an error: error: no rollout found. What is the most likely cause?

medium

A. Rollback command requires a namespace flag.

B. You misspelled the deployment name in the command.

C. The deployment 'myapp' has no previous versions to rollback to.

D. The Kubernetes cluster is down.

Solution

1. Step 1: Analyze the error message

   The error 'no rollout found' means no previous rollout history exists for rollback.

2. Step 2: Identify cause

   This usually happens if the deployment was never updated or has only one version.

3. Final Answer:

   The deployment 'myapp' has no previous versions to rollback to. -> Option C

4. Quick Check:

   No rollout history = no rollback possible [OK]

Hint: Check rollout history before rollback [OK]

Common Mistakes:

• Assuming cluster is down causes this error
• Forgetting to check deployment name spelling
• Thinking rollback always works without history

5. You have a deployment 'api-server' with three revisions in history. You want to rollback to revision 2 specifically. Which command should you use?

hard

A. kubectl rollout undo deployment/api-server revision=2

B. kubectl rollback deployment/api-server --revision=2

C. kubectl undo deployment/api-server revision 2

D. kubectl rollout undo deployment/api-server --to-revision=2

Solution

1. Step 1: Recall rollback to specific revision syntax

   The correct syntax to rollback to a specific revision is kubectl rollout undo deployment/<name> --to-revision=<number>.

2. Step 2: Apply to 'api-server' and revision 2

   Replacing placeholders gives kubectl rollout undo deployment/api-server --to-revision=2.

3. Final Answer:

   kubectl rollout undo deployment/api-server --to-revision=2 -> Option D

4. Quick Check:

   Use '--to-revision' flag to rollback specific version [OK]

Hint: Use '--to-revision' flag to rollback specific version [OK]

Common Mistakes:

• Using incorrect flags like --revision or wrong command order
• Omitting '--to-revision' flag
• Using 'rollback' instead of 'rollout undo'