Control the `update` order

Hello! I am running a service that uses leader elections. I’d love to be able to somehow save the active leader until last in the rolling update to prevent consecutive elections impacting the service. I don’t see an obvious native solution, has someone solved this without introducing a completely custom deploy?


1 Like

Just pop up this thread again. I have similar question. It is better to support rolling update strategy from newest to oldest OR from oldest to newest. Not sure if it is feasible or not.