kubectl port-forward for local access in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of kubectl port-forward command

What is the output when you run kubectl port-forward pod/myapp-pod 8080:80 successfully?

Kubernetes

kubectl port-forward pod/myapp-pod 8080:80

A Connection refused: unable to forward port

B Error from server (NotFound): pods "myapp-pod" not found

C Port 80 is already in use on localhost

D

Forwarding from 127.0.0.1:8080 -> 80
Forwarding from [::1]:8080 -> 80

💡 Hint

Successful port-forward shows the local and IPv6 forwarding lines.

When port-forward works, kubectl shows forwarding lines for localhost and IPv6 addresses.

🧠 Conceptual

intermediate

Purpose of kubectl port-forward

What is the main purpose of using kubectl port-forward in Kubernetes?

A To permanently expose a pod to external traffic

B To expose a pod's port locally without creating a service

C To scale the number of pod replicas

D To update the pod's container image

💡 Hint

Think about temporary local access to pod ports.

kubectl port-forward lets you access pod ports locally without exposing them externally or changing cluster resources.

❓ Troubleshoot

advanced

Troubleshooting port-forward connection refused error

You run kubectl port-forward pod/myapp-pod 8080:80 but get error: unable to forward port because connection refused. What is the most likely cause?

A kubectl is not installed on your machine

B The local port 8080 is already in use by another process

C The pod is not running or the container port 80 is not open

D The Kubernetes API server is down

💡 Hint

Check pod status and container ports.

Connection refused usually means the pod is not running or the target port inside the pod is not open.

🔀 Workflow

advanced

Correct kubectl port-forward command for service

You want to access port 5432 of a PostgreSQL service named db-service locally on port 15432. Which command is correct?

A kubectl port-forward svc/db-service 15432:5432

B kubectl port-forward pod/db-service 15432:5432

C kubectl expose svc/db-service --port=15432 --target-port=5432

D kubectl forward-port svc/db-service 5432:15432

💡 Hint

Remember to specify the resource type and correct port mapping.

To port-forward a service, use kubectl port-forward svc/servicename localPort:servicePort.

✅ Best Practice

expert

Best practice for secure kubectl port-forward usage

Which practice helps keep your local system secure when using kubectl port-forward?

A Use port-forward only on localhost and avoid exposing it to public networks

B Always forward ports to 0.0.0.0 to allow all network access

C Run port-forward with root privileges to avoid permission issues

D Disable firewall to ensure port-forward connections succeed

💡 Hint

Think about limiting network exposure.

Port-forward binds to localhost by default, which is safer. Avoid exposing forwarded ports to public networks to reduce risk.

Practice

1. What is the main purpose of kubectl port-forward in Kubernetes?

easy

A. To connect your local machine to a pod or service port inside the cluster

B. To expose a pod to the internet permanently

C. To create a new Kubernetes service

D. To delete a pod from the cluster

Solution

1. Step 1: Understand the function of port-forward

   kubectl port-forward creates a temporary tunnel from your local machine to a pod or service port inside the Kubernetes cluster.

2. Step 2: Compare other options

   Exposing pods permanently or creating/deleting resources are different commands and purposes.

3. Final Answer:

   To connect your local machine to a pod or service port inside the cluster -> Option A

4. Quick Check:

   Port-forward = local to pod/service connection [OK]

Hint: Port-forward = local access to pod/service port [OK]

Common Mistakes:

• Thinking port-forward exposes pods publicly
• Confusing port-forward with service creation
• Assuming it deletes pods

2. Which of the following is the correct syntax to forward local port 8080 to port 80 of a pod named my-pod?

easy

A. kubectl port-forward my-pod 80:8080

B. kubectl port-forward pod/my-pod 80:8080

C. kubectl port-forward my-pod 8080

D. kubectl port-forward pod/my-pod 8080:80

Solution

1. Step 1: Understand port-forward syntax

   The syntax is kubectl port-forward [resource-type/resource-name] localPort:remotePort. So to forward local 8080 to pod port 80, use 8080:80.

2. Step 2: Identify correct resource format

   Pod resource must be specified as pod/my-pod for clarity and correctness.

3. Final Answer:

   kubectl port-forward pod/my-pod 8080:80 -> Option D

4. Quick Check:

   Syntax = kubectl port-forward pod/name localPort:remotePort [OK]

Hint: Use pod/name and localPort:remotePort format [OK]

Common Mistakes:

• Reversing port numbers (remote:local instead of local:remote)
• Omitting 'pod/' prefix
• Swapping ports in the command

3. Given the command kubectl port-forward svc/my-service 9090:80, what will happen when you open http://localhost:9090 in your browser?

medium

A. You will access the pod's port 9090 directly

B. You will access the service's port 80 through local port 9090

C. You will get a connection refused error

D. The command will fail because services cannot be port-forwarded

Solution

1. Step 1: Understand port-forward to service

   The command forwards local port 9090 to port 80 of the service my-service. So accessing localhost:9090 connects to service port 80.

2. Step 2: Confirm service port-forward support

   Kubectl supports port-forwarding to services, so the command works and forwards traffic correctly.

3. Final Answer:

   You will access the service's port 80 through local port 9090 -> Option B

4. Quick Check:

   Port-forward svc port works = access via local port [OK]

Hint: Local port maps to service port, access via localhost:localPort [OK]

Common Mistakes:

• Thinking services cannot be port-forwarded
• Confusing local and remote ports
• Expecting pod port 9090 instead of service port 80

4. You run kubectl port-forward pod/my-pod 8080:80 but get the error: error: unable to forward port because pod is not running. What is the most likely cause?

medium

A. The pod my-pod is not in Running state

B. You used the wrong port numbers

C. Port-forward does not work with pods

D. You need to specify the namespace explicitly

Solution

1. Step 1: Analyze error message

   The error says the pod is not running, so port-forward cannot connect to it.

2. Step 2: Check pod state requirement

   Port-forward requires the pod to be in Running state to forward ports successfully.

3. Final Answer:

   The pod my-pod is not in Running state -> Option A

4. Quick Check:

   Pod must be Running for port-forward [OK]

Hint: Pod must be Running to port-forward [OK]

Common Mistakes:

• Assuming port numbers cause this error
• Thinking port-forward doesn't work with pods
• Ignoring pod status before port-forward

5. You want to access two different pods pod-a and pod-b running on ports 8080 and 9090 respectively, on your local machine at ports 3000 and 4000 simultaneously. Which commands should you run?

hard

A. kubectl port-forward pod/pod-a 3000:8080; kubectl port-forward pod/pod-b 4000:9090

B. kubectl port-forward pod/pod-a 8080:3000 & kubectl port-forward pod/pod-b 9090:4000

C. kubectl port-forward pod/pod-a 3000:8080 & kubectl port-forward pod/pod-b 4000:9090

D. kubectl port-forward pod/pod-a 3000:8080 pod/pod-b 4000:9090

Solution

1. Step 1: Understand port-forward syntax and concurrency

   Each port-forward command forwards one pod port to a local port. To run two simultaneously, run two commands in parallel using & or separate terminals.

2. Step 2: Verify port mappings

   Local port 3000 maps to pod-a's 8080, and local 4000 maps to pod-b's 9090. The syntax is localPort:remotePort.

3. Step 3: Check command correctness

   kubectl port-forward pod/pod-a 3000:8080 & kubectl port-forward pod/pod-b 4000:9090 correctly runs two commands in background with correct port mappings. kubectl port-forward pod/pod-a 3000:8080; kubectl port-forward pod/pod-b 4000:9090 runs sequentially, blocking second command.

4. Final Answer:

   kubectl port-forward pod/pod-a 3000:8080 & kubectl port-forward pod/pod-b 4000:9090 -> Option C

5. Quick Check:

   Run two port-forwards in parallel with correct local:remote ports [OK]

Hint: Run separate port-forward commands in background for multiple pods [OK]

Common Mistakes:

• Swapping local and remote ports
• Trying to port-forward multiple pods in one command
• Running commands sequentially blocking second port-forward