FlowFuse
Make deployments to HA instances sequential
Description
Currently when deploying a pipeline to a HA instance both instances are updated at the same time which leads to some downtime.
Customer would like to do the update to 1 instance at a time so that the flow is always available.
This would require picking one of the instances and waiting until it had finished deploying before triggering the restart on the second.
Customer: https://app-eu1.hubspot.com/contacts/26586079/record/0-2/18782320332?eschref=%2Fhelp-desk%2F26586079%2Fview%2F233410279%2Fticket%2F197680000210%2Fthread%2F13487366371
Which customers would this be available to
Enterprise Tier Only (EE)
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
@hardillb It seems that this issue will be solved by https://github.com/FlowFuse/flowfuse/issues/5554.
@gstout52 no they are totally unrelated, #5554 will have no impact on this
I’ve got a customer that is extremely sensitive to downtime and wants to push updates with effectively zero runtime interruption. I’ve asked about splitting their flows into many smaller instances to reduce blast radius, but that quickly gets into “too many instances” territory from their perspective.
Based on this thread it looks like we don’t currently support true zero-downtime deploys for a single logical app, and I don’t think we have a real workaround for this right now. Is that correct? I do have an idea for a workaround, but it would require them to rework how their flows are structured and would involve some manual management in the platform.
Link to Call: https://fathom.video/calls/472635510 Issue was raised over email.
