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.