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.