Init Containers

This article is a part of Kubernetes adventure series. If you wish to recieve further articles in this series please The kube guy

In our journey through Kubernetes, we’ve explored pods, services, deployments, and Ingress controllers, gaining a solid understanding of Operators and Ephemeral containers. Now, it’s time to dive into Init containers— the backstage heroes who work for completion. In this blog post, we’ll break down Init containers into simple terms, discuss their role, and demonstrate how they are used with an example at the end.

What Are Init Containers in Kubernetes?

In Kubernetes, think of a Pod as a tiny unit that can run one or more containers. Init containers are special containers within a Pod that get things ready before your main application container starts running. They are like the setup crew that prepares everything for a party before guests arrive. These containers run for completion. Each Init container completes the task before the other one initiates.If a Pod’s init container fails, the kubelet repeatedly restarts that init container until it succeeds..

Why Do We Use Init Containers?

Imagine you’re hosting a party. Before your guests (main application container) can enjoy the party, you need to do some prep work, like setting up decorations, getting food ready, and making sure the music is playing. Init containers do similar tasks for your application:

Setup Tasks: Init containers can do tasks like downloading important files, preparing databases, or fetching secret information.

Dependencies: Sometimes, your app needs other services to be ready, like a database. Init containers ensure these dependencies are in place before your app starts.

Delaying Start: You might want to wait for something to be ready, like an external service. Init containers help delay your app’s start until it’s the right time.

Common Scenarios for Init Containers:

Database Setup: Imagine you have a website that requires a database to store user information. You can use an Init container to make sure the database is set up and ready before your website starts running.

Fetching Configurations: Your app might need settings or configurations from outside sources. Init containers can fetch these for your app.

Waiting for Services: If your app relies on another service, like an external database, an init container can wait until that service is ready.

Scenario: You have a web application that relies on a database. Before your web application starts, you want to ensure the database is initialized and ready to accept connections.

Here’s an example YAML configuration for a Kubernetes Pod with an init container:

apiVersion: v1
kind: Pod
metadata:
 name: web-app-pod
spec:
 containers:
 — name: web-app-container
 image: web-app-image
 initContainers:
 — name: db-init
 image: postgresql-init-image

In this example:

web-app-container is your main application container, running the web app.
db-init is the init container responsible for initializing the database.
Now, let’s dive into what the db-init init container might do:

apiVersion: v1
kind: Pod
metadata:
 name: web-app-pod
spec:
 containers:
 — name: web-app-container
 image: web-app-image
 initContainers:
 — name: db-init
 image: postgresql-init-image
 command: [“/bin/sh”, “-c”]
 args:
 — |
 # Here, you can put your database initialization commands.
 # For example, setting up tables, users, and configurations.
 # Once the database is ready, this init container will exit.

In this db-init init container:

We use the command and args fields to specify the commands to run.
You’d typically put your database initialization commands in the args section. These commands might create tables, set up user permissions, or perform other database-related tasks.
The init container will continue running until it finishes its tasks. Once the database is properly initialized, the init container will exit, and the main web-app-container will start running.
So, in simple terms, the init container ensures that your database is set up correctly before your web application starts. This helps avoid any issues where your web app tries to connect to the database before it’s ready.

Conclusion:

Init containers are like the behind-the-scenes workers in a theatre, making sure everything is set up perfectly before the main show begins. They help ensure your applications in Kubernetes run smoothly, with all their requirements met. Whether it’s setting up databases, fetching configurations, or waiting for services, init containers are your go-to helpers for a successful Kubernetes party!