Executing commands in Pods in Kubernetes - Step-by-Step Execution

Process Flow - Executing commands in Pods

Start: Identify Pod

↓

Run kubectl exec command

↓

Connect to Pod container

↓

Execute command inside Pod

↓

Receive command output

↓

End

This flow shows how to run a command inside a Kubernetes Pod using kubectl exec, connecting to the container, executing the command, and getting the output.

Execution Sample

Kubernetes

kubectl exec my-pod -- ls /app
kubectl exec -it my-pod -- /bin/bash

These commands run 'ls /app' inside 'my-pod' and open an interactive bash shell inside the pod.

Process Table

Step	Command Run	Action	Result/Output
1	kubectl exec my-pod -- ls /app	Connect to 'my-pod' container	Connection established
2	kubectl exec my-pod -- ls /app	Run 'ls /app' inside pod	List of files/folders in /app
3	kubectl exec -it my-pod -- /bin/bash	Connect interactively to 'my-pod'	Interactive shell opened
4	kubectl exec -it my-pod -- /bin/bash	User types 'pwd' inside shell	/ (current directory)
5	kubectl exec -it my-pod -- /bin/bash	User types 'exit' to leave shell	Shell session ends

💡 Commands finish after output or user exits interactive shell

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Pod Connection	None	Connected	Connected	Interactive Connected	Interactive Connected	Disconnected
Command Output	None	None	File list	None	Current directory path	None

Key Moments - 2 Insights

Why do we use '--' before the command in 'kubectl exec'?

The '--' tells kubectl that what follows is the command to run inside the pod, not kubectl options. See execution_table steps 1 and 2.

What does the '-it' option do in 'kubectl exec -it'?

The '-i' keeps input open and '-t' allocates a terminal, allowing interactive commands like a shell. See execution_table steps 3 to 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the output after running 'kubectl exec my-pod -- ls /app'?

A Connection established

B List of files/folders in /app

C Interactive shell opened

D Shell session ends

💡 Hint

Check execution_table row 2 under 'Result/Output'

At which step does the user exit the interactive shell?

A Step 2

B Step 3

C Step 5

D Step 4

💡 Hint

Look at execution_table row 5 describing 'exit' command

If you remove '-it' from 'kubectl exec -it my-pod -- /bin/bash', what changes in the execution?

A You cannot interact; command runs non-interactively

B You still get an interactive shell

C Pod connection fails

D Command runs faster

💡 Hint

Refer to key_moments about '-it' option and execution_table steps 3-5

Concept Snapshot

kubectl exec <pod-name> -- <command>
- Runs a command inside a pod container
- Use '--' to separate kubectl options from command
- Add '-it' for interactive shell sessions
- Output shows command result or shell prompt
- Exit shell with 'exit' command

Full Transcript

Executing commands in Kubernetes pods uses the 'kubectl exec' command. First, identify the pod name. Then run 'kubectl exec pod-name -- command' to execute a command inside the pod. The '--' separates kubectl options from the command to run. For interactive sessions like a shell, add '-it' to keep input open and allocate a terminal. You connect to the pod container, run the command, and receive output. To exit an interactive shell, type 'exit'. This process helps you inspect or manage running pods easily.

Practice

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

easy

A. To list all Pods in a namespace

B. To create a new Pod

C. To run commands inside a running Pod

D. To delete a Pod

Solution

1. Step 1: Understand the function of kubectl exec

   The kubectl exec command is used to execute commands inside a running Pod's container.

2. Step 2: Differentiate from other commands

   Creating, deleting, or listing Pods are done with other commands like kubectl create, kubectl delete, and kubectl get.

3. Final Answer:

   To run commands inside a running Pod -> Option C

4. Quick Check:

   kubectl exec runs commands inside Pods [OK]

Hint: Remember: exec means execute inside Pod [OK]

Common Mistakes:

• Confusing exec with create or delete commands
• Thinking exec lists Pods
• Using exec to start new Pods

2. Which of the following is the correct syntax to run the command ls /app inside a Pod named web-pod?

easy

A. kubectl exec web-pod ls /app

B. kubectl exec web-pod -- ls /app

C. kubectl exec -- web-pod ls /app

D. kubectl exec -c web-pod ls /app

Solution

1. Step 1: Identify correct command separator

   The -- separates the Pod name from the command to run inside the Pod.

2. Step 2: Apply syntax rules

   The correct syntax is kubectl exec [pod-name] -- [command], so kubectl exec web-pod -- ls /app is correct.

3. Final Answer:

   kubectl exec web-pod -- ls /app -> Option B

4. Quick Check:

   Use -- before command [OK]

Hint: Use double dash (--) before command [OK]

Common Mistakes:

• Omitting the -- separator
• Placing -- before Pod name
• Using -c without container name

3. Given a Pod named db-pod with two containers: mysql and backup, what is the output of this command?

kubectl exec db-pod -c backup -- echo Hello

medium

A. Pod not found

B. Error: container name required

C. No such container: backup

D. Hello

Solution

1. Step 1: Understand the command components

   The command runs echo Hello inside the backup container of the db-pod Pod.

2. Step 2: Predict the command output

   Since the container exists and the command is valid, it outputs Hello.

3. Final Answer:

   Hello -> Option D

4. Quick Check:

   Correct container specified with -c outputs command result [OK]

Hint: Use -c to specify container, output is command result [OK]

Common Mistakes:

• Not specifying container when multiple exist
• Using wrong container name
• Expecting Pod name as container

4. You run this command but get an error:

kubectl exec mypod ls /data

What is the most likely cause?

medium

A. Missing -- before the command

B. Pod mypod does not exist

C. The ls command is invalid

D. You need to specify the container with -c

Solution

1. Step 1: Check command syntax

   The command is missing the -- separator between Pod name and command.

2. Step 2: Understand effect of missing --

   Without --, kubectl treats ls as a Pod or option, causing an error.

3. Final Answer:

   Missing -- before the command -> Option A

4. Quick Check:

   Always use -- before command [OK]

Hint: Always put -- before command to avoid errors [OK]

Common Mistakes:

• Forgetting the -- separator
• Assuming container must be specified when only one exists
• Thinking command is invalid

5. You want to run cat /etc/config inside the app-container of Pod multi-pod which has three containers. Which command is correct?

hard

A. kubectl exec multi-pod -c app-container -- cat /etc/config

B. kubectl exec multi-pod cat /etc/config -c app-container

C. kubectl exec -c app-container multi-pod cat /etc/config

D. kubectl exec multi-pod -- -c app-container cat /etc/config

Solution

1. Step 1: Identify correct order of options

   The -c option specifying the container must come after the Pod name and before the -- separator.

2. Step 2: Confirm command separator usage

   The -- must separate the Pod/container specification from the command to run.

3. Step 3: Validate each option

   kubectl exec multi-pod -c app-container -- cat /etc/config correctly places -c app-container before -- and then the command cat /etc/config.

4. Final Answer:

   kubectl exec multi-pod -c app-container -- cat /etc/config -> Option A

5. Quick Check:

   -c before --, then command [OK]

Hint: Put -c before --, then command [OK]

Common Mistakes:

• Placing -c after the command
• Putting -- before -c
• Omitting -- separator