Deployment status and history in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to check the status of a deployment named 'webapp'.

Kubernetes

kubectl get deployment [1]

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

Aservices

Bpods

Cwebapp

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' or 'services' instead of the deployment name.

Omitting the deployment name.

The command kubectl get deployment webapp shows the status of the deployment named 'webapp'.

2fill in blank

medium

Complete the command to view the rollout history of the deployment 'api-server'.

Kubernetes

kubectl rollout history deployment/[1]

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

Acache

Bdatabase

Cfrontend

Dapi-server

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong deployment name.

Forgetting to specify 'deployment/' before the name.

The command kubectl rollout history deployment/api-server shows the rollout history of the 'api-server' deployment.

3fill in blank

hard

Fix the error in the command to check the rollout status of deployment 'backend'.

Kubernetes

kubectl rollout [1] deployment/backend

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

Astatus

Bpause

Crestart

Dhistory

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'history' instead of 'status' to check current rollout.

Using unrelated subcommands like 'restart' or 'pause'.

The command kubectl rollout status deployment/backend checks the current rollout status of the 'backend' deployment.

4fill in blank

hard

Fill both blanks to create a command that shows the rollout history with revision details for deployment 'payment'.

Kubernetes

kubectl rollout history deployment/[1] --[2]

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

Apayment

Brevision

Cwatch

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong flags like '--watch' or '--status'.

Using wrong deployment names.

The command kubectl rollout history deployment/payment --revision shows detailed revision history for the 'payment' deployment.

5fill in blank

hard

Fill all three blanks to create a command that rolls back deployment 'frontend' to revision 3 and then checks its status.

Kubernetes

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

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

Arollback

Bfrontend

C3

Drestart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'restart' instead of 'rollback'.

Forgetting to specify the revision number.

Not repeating the deployment name in the second command.

The command kubectl rollout rollback deployment/frontend --to-revision=3 && kubectl rollout status deployment/frontend rolls back the 'frontend' deployment to revision 3 and then checks its rollout status.