Init containers in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Init Containers in Kubernetes

What is the main purpose of an init container in a Kubernetes Pod?

A To monitor the health of the main containers continuously

B To replace the main application containers

C To provide a user interface for the Pod

D To run setup tasks before the main containers start

💡 Hint

Think about tasks that must finish before the main app runs.

Init containers run before app containers to prepare the environment, like setting up files or waiting for services.

💻 Command Output

intermediate

Output of Pod Status with Init Container

Given a Pod with one init container that completes successfully and one main container running, what will be the Pod's status?

Kubernetes

kubectl get pod example-pod -o jsonpath='{.status.phase}'

A Pending

B Init

C Running

D Succeeded

💡 Hint

Consider what happens after init containers finish.

Once all init containers finish successfully, the Pod status moves to Running as main containers start.

❓ Configuration

advanced

Correct Init Container YAML Configuration

Which YAML snippet correctly defines an init container that runs a script before the main container?

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: init-example
spec:
  initContainers:
  - name: init-script
    image: busybox
    command: ["sh", "-c", "echo Init task done"]
  containers:
  - name: main-app
    image: nginx

A

initContainers:
- name: init-script
  image: busybox
  command: ["sh", "-c", "echo Init task done"]
containers:
- name: main-app
  image: nginx

B

containers:
- name: init-script
  image: busybox
  command: ["sh", "-c", "echo Init task done"]
initContainers:
- name: main-app
  image: nginx

C

initContainers:
- name: init-script
  image: busybox
  args: ["echo Init task done"]
containers:
- name: main-app
  image: nginx

D

initContainers:
- name: init-script
  image: busybox
  command: "echo Init task done"
containers:
- name: main-app
  image: nginx

💡 Hint

Check the correct use of command as a list and proper placement of initContainers.

Option A correctly places initContainers before containers and uses command as a list of strings.

❓ Troubleshoot

advanced

Troubleshooting Init Container Failure

A Pod's init container keeps restarting and never completes. What is the most likely cause?

A The main container image is missing

B The init container's command exits with a non-zero status

C The Pod has no resource limits set

D The Kubernetes node is out of disk space

💡 Hint

Think about what causes a container to restart repeatedly.

If the init container's command fails (non-zero exit), Kubernetes restarts it until success or failure limit.

🔀 Workflow

expert

Init Container Execution Order in Multi-Init Container Pod

Consider a Pod with three init containers named init1, init2, and init3. In what order will Kubernetes run these init containers?

A init1, then init2, then init3 sequentially

B All three init containers run in parallel

C init3, then init2, then init1 sequentially

D init1 and init3 run in parallel, then init2 runs last

💡 Hint

Think about whether init containers run at the same time or one after another.

Kubernetes runs init containers one by one in the order they are listed in the Pod spec.