traefik-on-service-fabric | Azure Service Fabric now has support for Traefik | Azure library

I will add my two cents to your considerations:

Is a preference between Dynamic and Static configuration.

The benefit is that it will reload with all the new configurations every time a service comes up with Traefik configuration. Today you say "it won't change", but in a few months, weeks or perhaps days, you might face a new requirement and you have to update the file, if the system evolves quickly, like on Microservices solution, you soon will face a hard work of updating this file by hand.

If you are sure it will hardly change, don't be limited by the Service Fabric Configuration or File, Traefik can get the configuration from REST , ETCD, DynamoDB and many other configuration providers to load the rules.

For the File approach, you can create the file in an Azure FileShare and mount as a volume in the container, so you don't need to rebuild the container to take effect.

Then you can just update the file and:

• Restart the container to reload the file, or.
• An even better approach is using the file.watch setting you don't need to restart the container and it will watch for any changes in the file.