Multi-container Pods concept in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Pod in Kubernetes?

A Pod is the smallest unit in Kubernetes that can run one or more containers together. It shares storage, network, and specifications for how to run the containers.

beginner

Why use multiple containers in a single Pod?

Multiple containers in one Pod work closely together, sharing resources like network and storage. This helps them cooperate, like a helper container managing logs or data for the main container.

intermediate

What is a sidecar container in a multi-container Pod?

A sidecar container is a helper container in the same Pod that supports the main container. For example, it can handle logging, data syncing, or proxying network requests.

beginner

How do containers in the same Pod communicate?

Containers in the same Pod share the same network space and can communicate using localhost and shared volumes for data exchange.

intermediate

What happens if one container in a multi-container Pod crashes?

If one container crashes, the whole Pod is affected. Kubernetes may restart the entire Pod depending on the restart policy.

What is the main reason to run multiple containers in a single Pod?

A To run unrelated applications in one Pod

B They share resources and work closely together

C To save memory by combining containers

D To avoid using Kubernetes services

Containers in a Pod share resources like network and storage and are designed to work closely together.

How do containers inside the same Pod communicate?

A Using localhost and shared volumes

B Through external IP addresses

C Using separate network namespaces

D They cannot communicate

Containers in the same Pod share the network namespace, so they communicate via localhost and can share data using volumes.

What is a sidecar container used for?

A To run a completely different application

B To replace the main container if it fails

C To help the main container with tasks like logging or proxying

D To increase the Pod's CPU limits

Sidecar containers assist the main container by handling supporting tasks.

If one container in a Pod crashes, what happens?

A The whole Pod may restart depending on the policy

B Only the crashed container restarts automatically

C The Pod continues running without changes

D Kubernetes deletes the Pod permanently

Kubernetes manages Pods as a unit, so if one container fails, the Pod may restart based on its restart policy.

Which of these is NOT true about multi-container Pods?

A Containers run on the same node

B Containers share the same IP address

C Containers can share storage volumes

D Containers have separate network namespaces

Containers in the same Pod share the network namespace; they do NOT have separate network namespaces.

Explain what a multi-container Pod is and why it is useful in Kubernetes.

Think about containers that help each other inside the same Pod.

Describe how containers inside the same Pod communicate and share data.

Imagine roommates sharing a house and talking face-to-face.

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