Priority of launching pod's - good practices

[radek_jasinski]

Hi,

Maybe any of you have experience on how to secure the Kubernetes environment in Azure, that in case of a reboot Dynatrace pods will always start first. I will point out that we are using the Full-Stack option.

For the moment, we used the "Pod priority" mechanisms, which only affects the scheduling of pods.

In addition, I found an example solution in the form of InitContainers. (https://medium.com/@xcoulon/initializing-containers-in-order-with-kubernetes-18173b9cc222). Unfortunately, this solution requires much more work and interference with the application pods.

Do we want to protect ourselves from situations such as manual restart the entire cluster to cause that non-DT pods start up in the wrong order? Then the solution remains for us to restart the application pods once again.

Thank you!

Radek

[pahofmann · Accepted solution]

If you are using the Operator, check out the cloudNativeFullStack mode. This will make sure the code modules are loaded before the pod comes up.