Certified Kubernetes Administrator (CKA) — Tips and Tricks — Part 5

Init Container is the way to do some setup task before the actual container starts 🏄‍♀

Init container is an important concept for the exam. There is a very high chance that this is one of your 24 questions. This blog will attempt to make you aware of the traps that you may get into and answer any form of init container question.

Init container containers are specialized containers that run before the normal containers in a Pod. Init containers generally contain setup scripts, that we are not able to make it as a part of our standard container. So when do we use init container? let’s look at a real-time example.

Init containers can be used to delay app container startup until a set of preconditions are met. Say we have to download a security key from the key vault, which we do not wish to make it as the past of our regular container for security reasons, then init container is the best choice. The below picture represents the above-mentioned scenarios.

The secret is downloaded and made available in a volume, for wich the main container will have access.

Some Facts

Below are some of the facts that we should know about init container.

  • We can have more than one init container in a pod
  • Init Containers always run to completion
  • Init Container executes in the order they are specified within the YAML definition
  • Each Init Container must complete successfully before the next one starts
  • If an init container fails, Kubernetes repeatedly restarts the Pod until the init container succeeds
  • Init containers do not support readiness probes because they must run to completion before the Pod can be ready.

Init Container YAML

Init Container YAML config looks very similar to standard container. I will have a name, image name with optional command and volume mount details. Init container documentations which can be accessed during the exam are available here

Init Container Image

The best way to use init containers is, creating an image and adding the necessary script to the docker file to do your task. But you don’t have an exam environment to do this task during the exam.

The way we should do in the exam is to use a dummy image name and then add a command attribute with all the necessary script representing the task that we wish to achieve. So which dummy image I use ❓ “busybox:1.28” come to the rescue. The above code snippet represents a simple task of init container, enabling sleep for a specified time, blocking the main container to start.

Shared Volume

For most of the requirements with Init Container, a shared volume between init container and application container is a key. In the exam, you may get a similar question involving shared volume. Let’s take a look at an example

Example: We should use Init Container to create a file named “sharedfile.txt” under the “work” directory and the application container should check if the file exists and sleep for a while. If the file does not exist the application container should exit.

Let have a full YAML view first and

emptyDir: {} — For Shared Volume

In the above example we are using “emptyDir: {}” for sharing volume between init container and application container. What is that ❓Documentation for the same is here at the Kubernetes documentation page which you can use during the exam. As mentioned in the Kubernetes documentation

“An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. As the name says, it is initially empty. Containers in the Pod can all read and write the same files in the emptyDir volume, though that volume can be mounted at the same or different paths in each Container. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever.”


Once you can create the Pod, we should validate if the pod is running and init container completed its task

Run “kubectl apply -f initpod.yaml”

then “kubectl describe pod init-container-test”

You can see the status of init container, you will see “Terminated” and reason as “Completed”. This shows that the init container completed its job successfully. You will also be able to see that the volume mount is created.

Debugging Errors

You may end up in errors, let’s see how to debug that. Update the in YAML @ init container section with the below line

This will fail the init container as we trying to use “mkdir1” a command which does not exist. Note the restart count indication.

Effectively use logs to identify the error. Look at init container error with

kubectl logs init-container-test init-container

That is all you need to know about init-container, we are done 🚀. Also, visit other tips and tricks for Certified Kubernetes Administrator (CKA)

We will look into other tips and tricks in an upcoming article. Let you pass with flying colors 🏄

#ContinuousDevOps #Kubernetes #Microservices #CloudNativeApps #DevOps #Agile