Kubernetes initContainers | Wait for MySQL to be running using initContainers

[@GrigoryRomanov]

Thanks, man! useful!

[@viveksinghggits]

Thank you. I am glad it was helpful.

[@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.

[@viveksinghggits]

Which image is being used in the initContainer, there are chances that image pull is taking more time than expected.
You can try to describe pod to figure out what's exactly is going on.

[@DiamantineRakib]

@@viveksinghggits thanks again for your reply. The init container is taking less time from second run.

[@viveksinghggits]

Cool, and I think because the image is already present.

[@yavinash007]

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

[@viveksinghggits]

Hi Avinash,
That's a good question. I haven't tried it but maybe having that command in a config map and then setting that as env var and eventually read thar env var in command should work.
I am not sure, but I think I have covered using env var values in command.

[@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

[@viveksinghggits]

Unfortunately I can’t create videos for these specific scenarios. You should try them by yourself and ask about the issues that you are facing.