Kubernetes initContainers | Wait for MySQL to be running using initContainers

In this video I looked into what are initContainers and some of the use cases why do we actually use them.
Later we actually modified our library application to run an initContiner that would run some dummy records in the database.

Web:

00:00 Introduction
00:26 Setup
00:35 What are initContainers
02:35 What do we mean by saying initContainers completing successfully
03:05 Differences between initContiners and main Containers
04:08 Use cases for initContainers
06:42 Specifying initContainers
07:54 Modifying library app to have initContainer that inserts some records into mysql database
11:56 Configuring initContainer for restapi deployment for library app
19:40 What happens when pod restart (idempotent code)
23:04 Like and Subscribe

[yavinash]

Thanks Vivek, quick question. The sequence of cmds you have in the "command" section of, the init container. Can they be read from a file/script, that can be reference here ?
For the sake of readability/debuggability, when those cmds become lengthy. Thanks

[DiamantineRakib]

thank you for your nice explanation. but in my case, the init container is taking too long to startup, it is taking more than 7 minutes, I have 5 deployments running each having a single pod. I am using minikube in my local environment.

[rohanekar]

Can you posible to create one video to create a Mysql microservice in Kubernetes and access this SQL using SQL workbench in the AWS EKS