In a Service Fabric cluster, during an application upgrade, Service Fabric follows certain upgrade domain (UD) rules to ensure that there is no downtime and the application remains available as much as possible. The behavior you're observing might be due to these rules and how the upgrade domains are being utilized.
Start-ServiceFabricApplicationUpgrade - works weird.
I have 3 Upgrade Domain (UD1, UD2, UD3) in cluster. My application (one instance) hosted in first UD1. When i run Start-ServiceFabricApplicationUpgrade -Monitored , application migrate on UD2 and UD1 upgraded. It`s OK. But when UD1 upgrade success and UD2 start upgrade, app migrate on UD3. Why? UD1 passed verification. Only when UD3 start upgrade, app migrate UD1
e. g. If I have 10 Domain Update then because of one instance, you have to wait for the update of all 10 UD?
I read https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-application-upgrade , but could not find an answer.