Init containers in Kubernetes - Mini Project: Build & Apply

Init Containers in Kubernetes

📖 Scenario: You are deploying a web application on Kubernetes. Before the main application container starts, you need to run an initialization task that sets up necessary files.

🎯 Goal: Create a Kubernetes Pod manifest with an initContainer that runs a simple setup command before the main container starts.

📋 What You'll Learn

Create a Pod manifest named webapp-pod.yaml

Add an initContainers section with one container named init-setup

The init-setup container should use the busybox image and run the command echo Setup complete

Add a main container named webapp using the nginx image

Ensure the initContainer runs before the main container

💡 Why This Matters

🌍 Real World

Init containers are used in Kubernetes to perform setup tasks like configuration, waiting for services, or preparing data before the main application starts.

💼 Career

Understanding init containers is essential for Kubernetes administrators and DevOps engineers to ensure reliable and ordered application startup.

1

Create the basic Pod manifest

Create a Kubernetes Pod manifest named webapp-pod.yaml with apiVersion set to v1, kind set to Pod, and metadata.name set to webapp. Add a spec section with a single container named webapp using the nginx image.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: webapp
spec:
  containers:
  - name: webapp
    image: nginx
# Your code here

Need a hint?

Start by defining the Pod with the required fields and add the main container under spec.containers.

2

Add the initContainer section

Add an initContainers section under spec with one container named init-setup. Use the busybox image and set the command to ["echo", "Setup complete"].

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: webapp
spec:
  initContainers:
  - name: init-setup
    image: busybox
    command: ["echo", "Setup complete"]
  containers:
  - name: webapp
    image: nginx
# Your code here

Need a hint?

The initContainers section goes at the same level as containers inside spec.

3

Verify the initContainer runs before the main container

Ensure the Pod manifest has initContainers defined before containers and that the init-setup container uses the busybox image with the command ["echo", "Setup complete"].

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: webapp
spec:
  initContainers:
  - name: init-setup
    image: busybox
    command: ["echo", "Setup complete"]
  containers:
  - name: webapp
    image: nginx
# Your code here

Need a hint?

Double-check the order and content of initContainers and containers in the manifest.

4

Display the Pod manifest

Print the complete Pod manifest to verify the initContainers and main container are correctly defined.

Kubernetes

# Print the Pod manifest
print(open('webapp-pod.yaml').read())

Need a hint?

Use a command or method to display the contents of webapp-pod.yaml.