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.

Practice

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

easy

A. It shows if the deployment named 'myapp' is successfully running or still updating.

B. It deletes the deployment named 'myapp' from the cluster.

C. It creates a new deployment named 'myapp'.

D. It lists all pods running in the cluster.

Solution

1. Step 1: Understand the command purpose

   The command kubectl rollout status checks the current status of a deployment rollout.

2. Step 2: Apply to the specific deployment

   Using deployment/myapp targets the deployment named 'myapp' to see if it is running or updating.

3. Final Answer:

   It shows if the deployment named 'myapp' is successfully running or still updating. -> Option A

4. Quick Check:

   Rollout status = Deployment running status [OK]

Hint: Use rollout status to check deployment health quickly [OK]

Common Mistakes:

• Confusing rollout status with deployment creation
• Thinking it deletes or lists pods
• Using wrong resource type after rollout status

2. Which of the following is the correct syntax to view the rollout history of a deployment named 'webapp'?

easy

A. kubectl get rollout history webapp

B. kubectl describe rollout webapp

C. kubectl rollout status deployment/webapp

D. kubectl rollout history deployment/webapp

Solution

1. Step 1: Identify the correct command for rollout history

   The command to view rollout history is kubectl rollout history.

2. Step 2: Use correct resource type and name

   Appending deployment/webapp specifies the deployment named 'webapp'.

3. Final Answer:

   kubectl rollout history deployment/webapp -> Option D

4. Quick Check:

   Rollout history syntax = kubectl rollout history deployment/name [OK]

Hint: Remember: rollout history shows past changes, rollout status shows current state [OK]

Common Mistakes:

• Using 'get' or 'describe' instead of 'rollout history'
• Omitting 'deployment/' prefix
• Confusing rollout status with rollout history

3. Given the command output:

deployment "frontend" successfully rolled out

What command was most likely run to get this output?

medium

A. kubectl get pods -l app=frontend

B. kubectl rollout history deployment/frontend

C. kubectl rollout status deployment/frontend

D. kubectl describe deployment frontend

Solution

1. Step 1: Analyze the output message

   The message says the deployment "frontend" was successfully rolled out, indicating a status check.

2. Step 2: Match output to command

   kubectl rollout status shows this success message, while history or describe commands show different outputs.

3. Final Answer:

   kubectl rollout status deployment/frontend -> Option C

4. Quick Check:

   Success rollout message = rollout status command [OK]

Hint: Success message means rollout status was checked [OK]

Common Mistakes:

• Confusing rollout history output with status output
• Assuming pod listing shows rollout success
• Using describe which shows detailed info, not status message

4. You ran kubectl rollout history deployment/api but got an error: error: deployments.apps "api" not found. What is the most likely cause?

medium

A. The Kubernetes cluster is down.

B. The deployment named 'api' does not exist in the current namespace.

C. You need to add '--all-namespaces' to see the deployment.

D. The command syntax is incorrect; 'rollout history' is invalid.

Solution

1. Step 1: Understand the error message

   The error says deployment "api" not found, meaning Kubernetes can't find that deployment in the current namespace.

2. Step 2: Check command and context

   The command syntax is correct, and cluster down would cause different errors. Missing deployment is the most likely cause.

3. Final Answer:

   The deployment named 'api' does not exist in the current namespace. -> Option B

4. Quick Check:

   Deployment not found error = deployment missing [OK]

Hint: Check deployment name and namespace if 'not found' error appears [OK]

Common Mistakes:

• Assuming syntax error when command is correct
• Forgetting namespace context
• Blaming cluster status without checking deployment

5. You want to rollback your deployment 'backend' to the previous version after a failed update. Which sequence of commands correctly checks the history and rolls back?

hard

A. kubectl rollout history deployment/backendkubectl rollout undo deployment/backend

B. kubectl rollout status deployment/backendkubectl delete deployment/backend

C. kubectl get pods -l app=backendkubectl rollout history deployment/backend

D. kubectl rollout undo deployment/backendkubectl rollout history deployment/backend

Solution

1. Step 1: Check rollout history

   Use kubectl rollout history deployment/backend to see past versions and confirm rollback target.

2. Step 2: Rollback to previous version

   Use kubectl rollout undo deployment/backend to revert to the last successful deployment.

3. Final Answer:

   kubectl rollout history deployment/backend followed by kubectl rollout undo deployment/backend -> Option A

4. Quick Check:

   History then undo = safe rollback steps [OK]

Hint: Always check history before undoing a rollout [OK]

Common Mistakes:

• Deleting deployment instead of rolling back
• Undoing before checking history
• Confusing status command with rollback