kubectl port-forward for local access in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to forward local port 8080 to pod port 80.

Kubernetes

kubectl port-forward [1] 8080:80

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

Aservice/my-service

Bpod/my-pod

Cdeployment/my-deploy

Dnode/my-node

Attempts:

3 left

💡 Hint

Common Mistakes

Using service or deployment instead of pod.

Omitting the resource type prefix.

You need to specify the pod name with pod/ prefix to forward ports directly to a pod.

2fill in blank

medium

Complete the command to forward local port 5000 to port 5000 of pod named 'web-app'.

Kubernetes

kubectl port-forward [1] 5000:5000

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

Apod/web-app

Bservice/web-app

Cpod/webapp

Ddeployment/web-app

Attempts:

3 left

💡 Hint

Common Mistakes

Using service or deployment instead of pod.

Misspelling the pod name.

The pod name must be exact and prefixed with pod/. Here, 'web-app' is the pod name.

3fill in blank

hard

Fix the error in the command to forward port 8080 to pod 'api-server'.

Kubernetes

kubectl port-forward [1] 8080:8080

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

Aapi-server

Bservice/api-server

Cpod/api-server

Ddeployment/api-server

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the resource type prefix.

Using service or deployment instead of pod.

The resource type pod/ must prefix the pod name to avoid errors.

4fill in blank

hard

Fill both blanks to forward local port 3000 to pod 'frontend' port 80 and local port 5000 to pod 'backend' port 5000.

Kubernetes

kubectl port-forward [1] 3000:80 & kubectl port-forward [2] 5000:5000

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

Apod/frontend

Bservice/frontend

Cpod/backend

Ddeployment/backend

Attempts:

3 left

💡 Hint

Common Mistakes

Using service or deployment instead of pod.

Mixing pod names between commands.

Use pod/frontend and pod/backend to forward ports directly to the pods.

5fill in blank

hard

Fill all three blanks to create a port-forward command that forwards local port 9090 to pod 'db' port 5432, and local port 8080 to pod 'cache' port 6379.

Kubernetes

kubectl port-forward [1] [2]:5432 & kubectl port-forward [3] 8080:6379

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

Apod/db

B9090

Cpod/cache

D5432

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping pod names or ports.

Using wrong port numbers or missing pod prefixes.

The first command forwards local port 9090 to pod 'db' port 5432. The second forwards local port 8080 to pod 'cache' port 6379.

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