Multi-container Pods concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Multi-container Pods

What is the main reason to use multiple containers inside a single Kubernetes Pod?

A To run tightly coupled containers that share resources and need to communicate closely

B To run completely independent applications that do not share any resources

C To increase the number of Pods running on a node without resource sharing

D To separate containers by namespaces for security isolation

💡 Hint

Think about containers that need to work together closely and share storage or network.

Multi-container Pods are designed to run containers that are tightly coupled and share the same network and storage. They communicate via localhost and share volumes.

💻 Command Output

intermediate

Output of Pod with Multiple Containers

Given this Pod YAML with two containers, what will be the output of kubectl get pods mypod -o jsonpath='{.spec.containers[*].name}'?

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: mypod
spec:
  containers:
  - name: app
    image: busybox
    command: ['sh', '-c', 'echo Hello from app']
  - name: sidecar
    image: busybox
    command: ['sh', '-c', 'echo Hello from sidecar']

A mypod app sidecar

B app sidecar

C app

D sidecar

💡 Hint

The command lists container names inside the Pod spec.

The jsonpath expression extracts all container names from the Pod spec, so it lists both 'app' and 'sidecar'.

❓ Configuration

advanced

Sharing Storage Between Containers in a Pod

Which volume configuration allows two containers in the same Pod to share files?

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: shared-pod
spec:
  containers:
  - name: container1
    image: busybox
    volumeMounts:
    - name: shared-data
      mountPath: /data
  - name: container2
    image: busybox
    volumeMounts:
    - name: shared-data
      mountPath: /data
  volumes:

A

  - name: shared-data
    emptyDir: {}

B

  - name: shared-data
    hostPath:
      path: /tmp/shared

C

  - name: shared-data
    configMap:
      name: shared-config

D

  - name: shared-data
    persistentVolumeClaim:
      claimName: pvc1

💡 Hint

Look for a volume type that creates a temporary directory shared in Pod lifetime.

emptyDir creates a temporary directory shared between containers in the same Pod, perfect for sharing files.

❓ Troubleshoot

advanced

Why Containers in a Pod Cannot Communicate

You have a Pod with two containers, but one container cannot reach the other on localhost. What is the most likely cause?

A Containers are in the same Pod but use different ports

B Containers are in the same Pod but use different volume mounts

C Containers are in the same Pod but have different images

D Containers are in different Pods, so they do not share the network namespace

💡 Hint

Remember that containers in the same Pod share network, but different Pods do not.

Containers in the same Pod share the network namespace and can communicate via localhost. If they are in different Pods, they cannot use localhost to communicate.

🔀 Workflow

expert

Order of Steps to Deploy a Multi-container Pod

Arrange the steps in the correct order to deploy a multi-container Pod and verify both containers are running.

A 2,1,3,4

B 1,3,2,4

C 1,2,3,4

D 1,2,4,3

💡 Hint

Think about writing config first, then applying it, then checking status, then logs.

You first write the YAML, then apply it to create the Pod, check if Pod is running, then check logs of each container.

Practice

1. What is the main purpose of having multiple containers inside a single Kubernetes Pod?

easy

A. To isolate containers completely from each other

B. To run containers on different nodes for load balancing

C. To run containers with different Kubernetes versions

D. To allow containers to share network and storage resources closely

Solution

1. Step 1: Understand Pod resource sharing

   Containers in the same Pod share network and storage, enabling close cooperation.

2. Step 2: Compare options

   Only To allow containers to share network and storage resources closely correctly describes this sharing. Other options describe different Kubernetes features.

3. Final Answer:

   To allow containers to share network and storage resources closely -> Option D

4. Quick Check:

   Multi-container Pods share resources = C [OK]

Hint: Pods share network/storage among containers [OK]

Common Mistakes:

• Thinking containers run on different nodes in one Pod
• Believing containers in a Pod are isolated
• Confusing Pod with Kubernetes version management

2. Which of the following is the correct way to define multiple containers inside a single Pod YAML spec?

easy

A. containers: [{name: 'app', image: 'app-image'}, {name: 'sidecar', image: 'sidecar-image'}]

B. container: [{name: 'app', image: 'app-image'}, {name: 'sidecar', image: 'sidecar-image'}]

C. containers: {name: 'app', image: 'app-image', name: 'sidecar', image: 'sidecar-image'}

D. pods: [{name: 'app', image: 'app-image'}, {name: 'sidecar', image: 'sidecar-image'}]

Solution

1. Step 1: Recall Pod spec syntax

   The Pod spec uses a key 'containers' with a list of container objects.

2. Step 2: Validate options

   containers: [{name: 'app', image: 'app-image'}, {name: 'sidecar', image: 'sidecar-image'}] correctly uses 'containers' as a list. The other options use wrong keys or wrong data structures.

3. Final Answer:

   containers: [{name: 'app', image: 'app-image'}, {name: 'sidecar', image: 'sidecar-image'}] -> Option A

4. Quick Check:

   Multiple containers use 'containers' list = A [OK]

Hint: Use 'containers' key with a list for multiple containers [OK]

Common Mistakes:

• Using 'container' instead of 'containers'
• Using curly braces instead of list for multiple containers
• Confusing 'pods' key with 'containers'

3. Given this Pod YAML snippet, what will be the output of kubectl get pods after applying it?

apiVersion: v1
kind: Pod
metadata:
  name: multi-container-pod
spec:
  containers:
  - name: app
    image: nginx
  - name: sidecar
    image: busybox
    command: ['sleep', '3600']

medium

A. Pod will fail because multiple containers are not allowed

B. Pod 'multi-container-pod' will be Running with two containers inside

C. Pod will be Pending indefinitely

D. Pod will run only the first container and ignore the second

Solution

1. Step 1: Analyze Pod spec

   The Pod defines two containers: 'app' running nginx and 'sidecar' running busybox sleep command.

2. Step 2: Understand Kubernetes behavior

   Kubernetes supports multiple containers in one Pod; both will run together. The Pod status will be Running if both containers start successfully.

3. Final Answer:

   Pod 'multi-container-pod' will be Running with two containers inside -> Option B

4. Quick Check:

   Multi-container Pod runs all containers = A [OK]

Hint: Multiple containers run together; Pod status shows Running if all start [OK]

Common Mistakes:

• Thinking multiple containers are not allowed in one Pod
• Assuming Pod stays Pending without reason
• Believing only one container runs per Pod

4. You created a Pod with two containers, but the second container keeps restarting. What is the most likely cause?

medium

A. The second container's command or image is incorrect causing crash loop

B. Kubernetes does not support more than one container per Pod

C. The Pod spec is missing the 'containers' key

D. The first container is using all CPU resources

Solution

1. Step 1: Identify container restart reasons

   Containers restart if their command fails or image is invalid, causing crash loops.

2. Step 2: Eliminate other options

   Kubernetes supports multiple containers per Pod. A missing 'containers' key causes Pod creation failure. Resource starvation usually affects all containers but does not cause restart loops.

3. Final Answer:

   The second container's command or image is incorrect causing crash loop -> Option A

4. Quick Check:

   Container restart loops = command/image error [OK]

Hint: Restart loops usually mean container command or image error [OK]

Common Mistakes:

• Believing Kubernetes disallows multiple containers
• Ignoring container command correctness
• Assuming resource usage causes restarts immediately

5. You want to add a logging container to your Pod that shares the same volume with the main app container. Which configuration is correct to achieve this?

hard

A. Mount the volume only in the logging container

B. Create separate volumes for each container and do not mount them

C. Define a shared volume under 'volumes' in Pod spec and mount it in both containers under 'volumeMounts'

D. Use different Pods for logging and app containers without shared volumes

Solution

1. Step 1: Understand volume sharing in Pods

   Volumes defined at Pod level can be mounted by multiple containers to share data.

2. Step 2: Check options for volume usage

   Define a shared volume under 'volumes' in Pod spec and mount it in both containers under 'volumeMounts' correctly defines a shared volume and mounts it in both containers. Other options either separate volumes or do not mount properly, preventing sharing.

3. Final Answer:

   Define a shared volume under 'volumes' in Pod spec and mount it in both containers under 'volumeMounts' -> Option C

4. Quick Check:

   Shared volumes require Pod-level volume and mounts in containers [OK]

Hint: Share volumes by defining once and mounting in all containers [OK]

Common Mistakes:

• Defining separate volumes for each container
• Not mounting volumes in all containers needing access
• Using separate Pods instead of multi-container Pod