Why kubectl mastery matters in Kubernetes - See It in Action

Why kubectl mastery matters

📖 Scenario: You are a new DevOps engineer starting to manage applications on Kubernetes clusters. You need to understand how to use kubectl, the command-line tool for Kubernetes, to interact with your cluster resources effectively.

🎯 Goal: Learn the basics of kubectl commands by creating a simple pod, checking its status, and listing pods in the cluster. This will help you gain confidence in managing Kubernetes resources.

📋 What You'll Learn

Create a YAML file defining a simple pod named my-pod running the nginx container

Use kubectl to create the pod from the YAML file

Use kubectl to check the status of my-pod

Use kubectl to list all pods in the default namespace

💡 Why This Matters

🌍 Real World

In real work, DevOps engineers use <code>kubectl</code> daily to deploy, monitor, and troubleshoot applications running on Kubernetes clusters.

💼 Career

Mastering <code>kubectl</code> commands is essential for roles like Kubernetes administrator, DevOps engineer, and cloud engineer to manage containerized applications effectively.

1

Create a pod YAML file

Create a file named my-pod.yaml with the exact content below to define a pod named my-pod running the nginx container:

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: nginx
    image: nginx

Kubernetes

# Create the file my-pod.yaml with the pod definition
# Your code here

Hint

Make sure the file is named exactly my-pod.yaml and the indentation matches YAML format.

2

Create the pod using kubectl

Run the exact command kubectl apply -f my-pod.yaml to create the pod in your Kubernetes cluster.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: nginx
    image: nginx

# Run the command to create the pod
# Your code here

Hint

Use kubectl apply -f followed by the YAML file name to create resources.

3

Check the pod status

Run the exact command kubectl get pod my-pod to see the status of the pod named my-pod.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: nginx
    image: nginx

kubectl apply -f my-pod.yaml

# Run the command to check pod status
# Your code here

Hint

Use kubectl get pod followed by the pod name to check its status.

4

List all pods in the default namespace

Run the exact command kubectl get pods to list all pods running in the default namespace.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: nginx
    image: nginx

kubectl apply -f my-pod.yaml

kubectl get pod my-pod

# Run the command to list all pods
# Your code here

Hint

Use kubectl get pods to see all pods. The output should show my-pod with status Running.

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