Understand if reloader handles memory allocation on rolling restart

[varshapathak31000]

Hi Reloader community, Thank you for taking out time to read this. I want to confirm few things wrt Reloader before we adopt it for all our services.

1. Reloader does rolling restart of pods?
2. What happens if pods exhaustion limit is hit while restarting? If yes, is there a way to handle the same?
3. Does reloader restart all deployments at once, or is it done sequentially? Thank you in advance. Regards, Varsha Pathak

[faizanahmad055]

Hi,

Just to make it simpler, the reloader doesn't interact with the pod at all. Reloader interacts with the parent resource (deployment, statefulset). It does that by updating the deployment (parent resource) and which results in the pod being restarted. The behaviour is very easy to test. If you modify your deployment manually like adding an extra env, whatever the behaviour will be in that case, will be the behaviour with reloader because that's what reloader does i.e. modify the deployment. So how the pod restarts, whether it is a rolling update or recreate all at once, it depends on how your deployment is configured. Reloader doesn't play any role in that.

[karl-johan-grahn]

@varshapathak31000 are you ok with us closing this?