Forum Discussion
How to Migrate An Existing DataGateway with PowerShell
I don't know the background or the cost considerations of "each time when this instance is restarted or a new instance is provisioned" but I would look for something more permanent to avoid having to redo the gateway all the time. If you have multiple cluster members the load balancer will give the job to whichever cluster member is available, without a business interruption.
So, yes having a cluster mode with a load balancer is the best solution for resiliency and high-availability for sure. However, same problem will occur if we would like to have a code pipeline with a basic blue/green deployment. Instances might get replaced when there is a software update or even die. What I see microsoft doesn't provide a simple solution to fully automate this process easily which always requires a manual intervention.
You can always add/remove cluster members from the logical configuration (regardless of their physical status). Where it gets (extremely) hairy is when you remove the last ("anchor") cluster member. That's when your entire gateway goes "poof".
Yeap, adding/removing members came into my mind after you introduced cluster mode idea, but that poof moment will put me in a hard situation. I think that can be avoided easily though by removing an offline member after adding the new one. Nevertheless, the annoying part is there is no any REST api or cmdlet that allows migrating a data gateway...
If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com