Kubectl for cluster management in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all pods in the current Kubernetes cluster.

Azure

kubectl [1] pods

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

Acreate

Bget

Cdelete

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'get' will try to create a resource.

Using 'delete' will remove resources, not list them.

The kubectl get pods command lists all pods in the current cluster.

2fill in blank

medium

Complete the command to switch the current context to a cluster named 'prod-cluster'.

Azure

kubectl config [1] prod-cluster

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

Adelete-context

Bset-context

Cuse-context

Dget-contexts

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'set-context' modifies context settings but does not switch the active context.

Using 'get-contexts' only lists available contexts.

The command kubectl config use-context prod-cluster switches the active cluster context to 'prod-cluster'.

3fill in blank

hard

Fix the error in the command to delete a pod named 'web-server'.

Azure

kubectl [1] pod web-server

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

Aremove

Bdestroy

Cterminate

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'remove' or 'destroy' causes command errors because they are not kubectl verbs.

Forgetting to specify the resource type 'pod' can cause errors.

The correct command to delete a pod is kubectl delete pod web-server. Other verbs like 'remove' or 'destroy' are not valid kubectl commands.

4fill in blank

hard

Fill both blanks to describe the command that shows detailed information about a pod named 'db-server'.

Azure

kubectl [1] pod [2] -o yaml

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

Adescribe

Bdb-server

Cget

Dlist

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' instead of 'describe' shows less detail.

Using 'list' is not a valid kubectl command.

The command kubectl describe pod db-server -o yaml shows detailed information about the pod in YAML format.

5fill in blank

hard

Fill all three blanks to create a deployment named 'frontend' using the image 'nginx:latest' with 3 replicas.

Azure

kubectl create deployment [1] --image=[2] --replicas=[3]

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

Afrontend

Bnginx:latest

C3

Dbackend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'backend' instead of 'frontend' changes the deployment name.

Forgetting to specify the number of replicas defaults to 1.

The command kubectl create deployment frontend --image=nginx:latest --replicas=3 creates a deployment named 'frontend' with 3 replicas of the nginx image.

Practice

1. What is the primary purpose of the kubectl tool in Kubernetes?

easy

A. To manage and control Kubernetes clusters

B. To create virtual machines in Azure

C. To monitor network traffic outside the cluster

D. To write application code for Kubernetes

Solution

1. Step 1: Understand kubectl's role

   kubectl is designed to interact with Kubernetes clusters to manage resources like pods, deployments, and services.

2. Step 2: Compare options

   Options A, B, and C describe tasks unrelated to kubectl. Only To manage and control Kubernetes clusters correctly states its purpose.

3. Final Answer:

   To manage and control Kubernetes clusters -> Option A

4. Quick Check:

   kubectl = cluster management [OK]

Hint: kubectl controls Kubernetes clusters directly [OK]

Common Mistakes:

• Confusing kubectl with Azure VM tools
• Thinking kubectl writes application code
• Assuming kubectl monitors external network traffic

2. Which of the following is the correct syntax to list all pods in the current Kubernetes namespace using kubectl?

easy

A. kubectl get pods

B. kubectl list pods

C. kubectl show pods

D. kubectl describe pods

Solution

1. Step 1: Recall kubectl commands for listing resources

   The command to list resources is kubectl get, followed by the resource type.

2. Step 2: Evaluate options

   Only kubectl get pods uses the correct syntax kubectl get pods. Options A and B are invalid commands, and D shows detailed info, not a simple list.

3. Final Answer:

   kubectl get pods -> Option A

4. Quick Check:

   List pods = kubectl get pods [OK]

Hint: Use 'kubectl get' to list Kubernetes resources [OK]

Common Mistakes:

• Using 'list' or 'show' instead of 'get'
• Confusing 'describe' with listing
• Adding extra words after 'pods'

3. Given the command kubectl get pods -o wide, what extra information will you see compared to kubectl get pods?

medium

A. Detailed pod logs

B. Extended pod information including node and IP

C. Only pod names without status

D. List of services instead of pods

Solution

1. Step 1: Understand the '-o wide' option

   The -o wide flag shows additional columns like node name and pod IP address.

2. Step 2: Compare output differences

   Extended pod information including node and IP correctly describes the extra info. Detailed pod logs is about logs, not shown here. Only pod names without status is incorrect as status is shown by default. List of services instead of pods is unrelated.

3. Final Answer:

   Extended pod information including node and IP -> Option B

4. Quick Check:

   -o wide = more pod details [OK]

Hint: Use '-o wide' to see node and IP info for pods [OK]

Common Mistakes:

• Thinking '-o wide' shows logs
• Assuming it hides status info
• Confusing pods with services

4. You run kubectl get pod mypod but get an error saying the pod does not exist. What is the most likely cause?

medium

A. You are in the wrong namespace

B. The pod name is misspelled

C. The pod has already been deleted

D. All of the above

Solution

1. Step 1: Check common reasons for pod not found error

   The error can happen if the pod name is wrong, the pod was deleted, or you are looking in the wrong namespace.

2. Step 2: Evaluate options

   All options B, C, and D are valid causes. Therefore, All of the above which includes all is correct.

3. Final Answer:

   All of the above -> Option D

4. Quick Check:

   Pod not found = wrong namespace, name, or deleted [OK]

Hint: Check namespace, spelling, and pod existence [OK]

Common Mistakes:

• Ignoring namespace context
• Assuming pod always exists
• Not verifying pod name spelling

5. You want to update the image of a deployment named webapp to version v2 using kubectl. Which command correctly performs this update?

hard

A. kubectl update deployment webapp --image=webapp:v2

B. kubectl edit deployment webapp image=webapp:v2

C. kubectl set image deployment/webapp webapp=webapp:v2

D. kubectl change image webapp webapp:v2

Solution

1. Step 1: Identify the correct kubectl command to update deployment image

   The command kubectl set image is used to update container images in deployments.

2. Step 2: Analyze each option

   kubectl set image deployment/webapp webapp=webapp:v2 uses correct syntax: kubectl set image deployment/webapp webapp=webapp:v2. Options A, C, and D use invalid or incorrect commands.

3. Final Answer:

   kubectl set image deployment/webapp webapp=webapp:v2 -> Option C

4. Quick Check:

   Update image = kubectl set image [OK]

Hint: Use 'kubectl set image' to update deployment containers [OK]

Common Mistakes:

• Using 'kubectl update' which is invalid
• Trying 'kubectl edit' without proper syntax
• Using non-existent 'kubectl change' command