Init containers, which RUN before application containers and can contain utilities or setup scripts not available in an app image, are provided by the OpenShift Container Platform. Before the rest of a pod is deployed, you can utilise an Init Container resource to conduct activities.

In addition to application containers, a pod can have Init Containers. Setup scripts and binding code can be reorganised using init containers. An Init Container can do the following:

• Contain and run utilities that, for security reasons, should not be included in the app Container image.
• Contains setup tools or custom code that isn't included in the app image. For example, using sed, awk, python, or dig during setup does not necessitate creating an image FROM another picture.
• Use Linux namespaces to provide them DIFFERENT filesystem views than app containers, including access to SECRETS that app containers don't have.

Before the next Init Container is STARTED, the PREVIOUS one must finish successfully. As a result, Init Containers make it simple to prevent or delay the launch of app containers until certain conditions are met.