Pod-to-Pod communication in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Pod that listens on port 80.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  containers:
  - name: web
    image: nginx
    ports:
    - containerPort: [1]

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

A443

B8080

C22

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 8080 instead of 80

Using port 443 which is for HTTPS

Using port 22 which is for SSH

The standard HTTP port is 80, so the container should listen on port 80 for web traffic.

2fill in blank

medium

Complete the command to check the IP address of a Pod named 'my-pod'.

Kubernetes

kubectl get pod my-pod -o [1]

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

Ajsonpath='{.status.phase}'

Bwide

Cjsonpath='{.status.podIP}'

Dyaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'wide' which shows more info but not just the IP

Using 'yaml' which outputs full YAML

Using jsonpath for phase instead of podIP

The jsonpath option with '{.status.podIP}' extracts the Pod's IP address.

3fill in blank

hard

Fix the error in the Service definition to expose port 80 correctly.

Kubernetes

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  selector:
    app: my-app
  ports:
  - protocol: TCP
    port: [1]
    targetPort: 8080

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

A8080

B80

C22

D443

Attempts:

3 left

💡 Hint

Common Mistakes

Setting port to 8080 which is the container port, not the service port

Using port 22 or 443 which are for SSH and HTTPS

The Service port should be 80 to expose the application on the standard HTTP port, while targetPort can be different.

4fill in blank

hard

Fill both blanks to create a NetworkPolicy that allows ingress only from Pods with label 'role=frontend'.

Kubernetes

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-frontend
spec:
  podSelector: {}
  ingress:
  - from:
    - podSelector:
        matchLabels:
          [1]: [2]

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

Arole

Bfrontend

Capp

Dbackend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'app' instead of 'role' as label key

Using 'backend' instead of 'frontend' as label value

The NetworkPolicy allows ingress from Pods labeled with 'role=frontend'.

5fill in blank

hard

Fill all three blanks to create a ConfigMap with keys 'host' and 'port'.

Kubernetes

apiVersion: v1
kind: ConfigMap
metadata:
  name: service-config
data:
  [1]: example.com
  [2]: "[3]"

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

Ahost

Bport

Chttp

Dprotocol

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up keys and values

Not quoting the port value as a string

The ConfigMap defines 'host' as example.com and 'port' as 'http'.

Practice

1.

How do pods inside a Kubernetes cluster typically communicate with each other?

easy

A. Using external DNS names only

B. Using pod IP addresses or service names

C. Through direct access to the host machine's network

D. By sharing the same storage volume

Solution

1. Step 1: Understand pod networking basics

   Pods have their own IP addresses inside the cluster and can communicate directly using these IPs.

2. Step 2: Recognize the role of services

   Services provide stable DNS names to reach pods even if pod IPs change.

3. Final Answer:

   Using pod IP addresses or service names -> Option B

4. Quick Check:

   Pod communication = IP or service name [OK]

Hint: Pods use IPs or services to talk inside cluster [OK]

Common Mistakes:

• Thinking pods use external DNS only
• Assuming pods share host network by default
• Believing storage volumes enable communication

2.

Which of the following is the correct way to define a Kubernetes Service to expose pods for pod-to-pod communication?

apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  selector:
    app: myapp
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080

easy

A. The service exposes port 8080 externally but does not select pods

B. The selector matches pods with label app: myapp but ports are reversed

C. The selector matches pods with label app: myapp and forwards port 80 to 8080

D. The service definition is missing the type field, so it won't work

Solution

1. Step 1: Check the selector field

   The selector app: myapp correctly matches pods with that label.

2. Step 2: Verify ports mapping

   Port 80 on the service forwards traffic to port 8080 on the pods, which is correct.

3. Final Answer:

   The selector matches pods with label app: myapp and forwards port 80 to 8080 -> Option C

4. Quick Check:

   Selector and ports correct = The selector matches pods with label app: myapp and forwards port 80 to 8080 [OK]

Hint: Selector matches pod labels; ports map service to pod [OK]

Common Mistakes:

• Confusing port and targetPort roles
• Thinking 'type' is mandatory for basic service
• Ignoring selector means no pods matched

3.

Given two pods in the same namespace, pod-a and pod-b, where pod-b runs a web server on port 80, what is the expected output of this command run inside pod-a?

curl http://pod-b:80

Assuming pod-b is reachable by its pod IP but not by name.

medium

A. Connection refused or host not found error

B. Successful HTTP response from pod-b's web server

C. Timeout error because pods cannot communicate

D. DNS resolution error for pod-b

Solution

1. Step 1: Understand pod DNS naming

   Pods do not have DNS names by default; only services have stable DNS names.

2. Step 2: Analyze the command

   Trying to curl pod-b by name will fail DNS resolution because pod names are not DNS entries.

3. Final Answer:

   DNS resolution error for pod-b -> Option D

4. Quick Check:

   Pod names not DNS = DNS resolution error [OK]

Hint: Pod names are not DNS names; use service names [OK]

Common Mistakes:

• Assuming pod names resolve in DNS
• Expecting direct pod name communication
• Ignoring need for service abstraction

4.

You have a service named backend exposing pods on port 8080. A pod tries to connect using curl http://backend:80 but gets a connection refused error. What is the likely cause?

medium

A. The service port is 8080, but curl uses port 80

B. The service selector does not match any pods

C. The pod network is not enabled

D. The service type is NodePort instead of ClusterIP

Solution

1. Step 1: Check service port configuration

   The service exposes port 8080, but the curl command targets port 80, causing connection refusal.

2. Step 2: Understand port mapping importance

   Clients must use the service port, not the pod's internal port, to connect successfully.

3. Final Answer:

   The service port is 8080, but curl uses port 80 -> Option A

4. Quick Check:

   Port mismatch causes connection refused [OK]

Hint: Match curl port to service port exactly [OK]

Common Mistakes:

• Ignoring port mismatch between service and client
• Assuming network is disabled without checking
• Confusing service types with connectivity issues

5.

You want to ensure stable pod-to-pod communication in a Kubernetes cluster where pods restart frequently and get new IPs. Which approach best solves this problem?

hard

A. Use a Kubernetes Service to provide a stable DNS name and load balancing

B. Use pod IP addresses directly in application configuration

C. Configure pods to share the same static IP address

D. Use host networking mode for all pods

Solution

1. Step 1: Identify the problem with pod IPs

   Pods get new IPs on restart, so direct IP communication is unstable.

2. Step 2: Use Kubernetes Service for stability

   Services provide a stable DNS name and load balancing to reach pods regardless of IP changes.

3. Step 3: Evaluate other options

   Static IPs for pods are not practical; host networking breaks isolation; direct IP use is unreliable.

4. Final Answer:

   Use a Kubernetes Service to provide a stable DNS name and load balancing -> Option A

5. Quick Check:

   Service = stable pod communication [OK]

Hint: Use services for stable pod communication despite IP changes [OK]

Common Mistakes:

• Hardcoding pod IPs in configs
• Trying to assign static IPs to pods
• Using host networking unnecessarily