Why kubectl mastery matters in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all pods in the current namespace.

Kubernetes

kubectl get [1]

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

Aservices

Bpods

Cnodes

Ddeployments

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl get nodes' lists nodes, not pods.

Using 'kubectl get services' lists services, not pods.

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

2fill in blank

medium

Complete the command to describe a pod named 'web-server'.

Kubernetes

kubectl [1] pod web-server

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

Adescribe

Bdelete

Clist

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl list' which is not a valid command.

Using 'kubectl delete' which removes the pod.

The kubectl describe pod web-server command shows detailed information about the pod named 'web-server'.

3fill in blank

hard

Fix the error in the command to scale a deployment named 'frontend' to 3 replicas.

Kubernetes

kubectl scale deployment frontend --replicas=[1]

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

Atwo

Bzero

C-3

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Using words like 'two' or 'zero' instead of numbers.

Using negative numbers which are invalid.

The replicas count must be a positive integer. Using 3 correctly scales the deployment to 3 replicas.

4fill in blank

hard

Fill both blanks to create a pod manifest file named 'pod.yaml' using kubectl.

Kubernetes

kubectl [1] pod nginx --dry-run=client -o [2] > pod.yaml

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

Acreate

Bapply

Cyaml

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'apply' instead of 'create' for generating manifests.

Using 'json' output when YAML is preferred for manifests.

The command kubectl create pod nginx --dry-run=client -o yaml generates a pod manifest in YAML format without creating it.

5fill in blank

hard

Fill all three blanks to get logs from a pod named 'backend' for container 'app' with 100 lines.

Kubernetes

kubectl logs [1] -c [2] --tail=[3]

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

Abackend

Bapp

C100

Dfrontend

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong pod or container names.

Omitting the container name when multiple containers exist.

The command kubectl logs backend -c app --tail=100 fetches the last 100 lines of logs from the 'app' container in the 'backend' pod.

Practice

1. Why is mastering kubectl important when working with Kubernetes?

easy

A. It is only used for installing Kubernetes.

B. It allows you to quickly view and manage your Kubernetes resources.

C. It replaces the need to understand Kubernetes concepts.

D. It automatically fixes all errors in your Kubernetes cluster.

Solution

1. Step 1: Understand the role of kubectl

   kubectl is the main command-line tool to interact with Kubernetes clusters.

2. Step 2: Recognize its practical use

   It helps you view, update, and manage your apps and resources quickly and efficiently.

3. Final Answer:

   It allows you to quickly view and manage your Kubernetes resources. -> Option B

4. Quick Check:

   kubectl = manage Kubernetes resources fast [OK]

Hint: kubectl is your hands-on tool to control Kubernetes [OK]

Common Mistakes:

• Thinking kubectl fixes errors automatically
• Believing kubectl replaces Kubernetes knowledge
• Assuming kubectl is only for installation

2. Which of the following kubectl commands is correctly written to list all pods in the default namespace?

easy

A. kubectl get pods

B. kubectl list pods

C. kubectl show pods

D. kubectl pods get

Solution

1. Step 1: Recall the correct command syntax

   The correct command to list pods is kubectl get pods.

2. Step 2: Identify incorrect options

   Commands like list, show, or reversed order are invalid in kubectl.

3. Final Answer:

   kubectl get pods -> Option A

4. Quick Check:

   List pods = kubectl get pods [OK]

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

Common Mistakes:

• Using 'list' or 'show' instead of 'get'
• Reversing command order
• Omitting 'get' keyword

3. What will be the output of the command kubectl get pods myapp-pod -o wide if the pod exists?

medium

A. Only the pod name will be displayed.

B. An error saying pod not found.

C. Detailed information about the pod including node and IP address.

D. The pod will be deleted.

Solution

1. Step 1: Understand the command options

   -o wide shows extra details like node and IP for the pod.

2. Step 2: Confirm pod existence effect

   If the pod exists, kubectl displays its detailed info; no error or deletion occurs.

3. Final Answer:

   Detailed information about the pod including node and IP address. -> Option C

4. Quick Check:

   kubectl get pod -o wide = detailed pod info [OK]

Hint: Use '-o wide' for extra pod details [OK]

Common Mistakes:

• Expecting deletion from get command
• Thinking only pod name shows
• Assuming error if pod exists

4. You run kubectl apply -f deployment.yaml but get an error: "error: unable to recognize \"deployment.yaml\": no matches for kind \"Deploymnt\"". What is the likely cause?

medium

A. kubectl is not installed.

B. The file path is incorrect.

C. The cluster is down.

D. The kind field in the YAML file is misspelled.

Solution

1. Step 1: Analyze the error message

   The error says "no matches for kind \"Deploymnt\"", indicating a typo in the resource kind.

2. Step 2: Understand kubectl behavior

   kubectl cannot recognize the misspelled kind, so it fails to apply the file.

3. Final Answer:

   The kind field in the YAML file is misspelled. -> Option D

4. Quick Check:

   Typo in kind causes apply error [OK]

Hint: Check spelling of 'kind' in YAML files [OK]

Common Mistakes:

• Assuming file path error without checking content
• Thinking kubectl installation causes this error
• Blaming cluster status without error details

5. You want to update a running deployment named webapp to use a new image version webapp:v2 without downtime. Which kubectl command should you use?

hard

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

B. kubectl delete deployment webapp && kubectl create deployment webapp --image=webapp:v2

C. kubectl apply -f webapp-v2.yaml without changing image

D. kubectl scale deployment webapp --replicas=0

Solution

1. Step 1: Identify the goal

   You want to update the image of the deployment without downtime, meaning a rolling update.

2. Step 2: Choose the correct kubectl command

   kubectl set image deployment/webapp webapp=webapp:v2 updates the image and triggers a rolling update safely.

3. Step 3: Understand why other options fail

   Deleting and recreating causes downtime; applying without image change does nothing; scaling to zero stops pods.

4. Final Answer:

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

5. Quick Check:

   Use 'kubectl set image' for zero-downtime update [OK]

Hint: Use 'kubectl set image' for rolling updates [OK]

Common Mistakes:

• Deleting deployment causes downtime
• Applying without image change does not update
• Scaling to zero stops the app