Service Fabric Mesh Preview Refresh Release


We're excited to announce that the Service Fabric Mesh Preview runtime, SDK, and tooling updates are now available. These releases were announced at Ignite earlier this year, and over the next few of days, the updates will be available in all the Azure regions.

What's new in the Service Fabric Mesh preview refresh?

  • Services can now be automatically scaled by specifying CPU and memory thresholds in the application model.
  • Ability to specify and use inline secrets in the application model.
  • Support multiple ingress for per-request routing to services.
  • Support for mounting Azure Files storage as a volume to be used in containers.
  • Support for Service Fabric Reliable Volumes that provide high availability through built-in replication.
  • Maven CLI integration for easily creating and deploying Mesh applications.
  • Browse & manage Mesh applications through the Azure portal.

We've also updated the Visual Studio Service Fabric Mesh Tools (Preview) with the following capabilities.

  • Ability to add Mesh support to existing ASP.NET Framework and .NET console projects.
  • Support for targeting multiple environments via the use of parameters.
  • Support for Gateway, Service Fabric Reliable Volume, and Azure Files Volume resources.

The new tooling will work against local Service Fabric 6.4 clusters. As the rollout proceeds, the tooling will work against Mesh environments in Azure as well. To check which regions have been updated, please run the following command in PowerShell:

Get-AzureRmResourceProvider -ProviderNamespace "Microsoft.ServiceFabricMesh" | ? {$_.ResourceTypes.ResourceTypeName -eq "gateways" } | % { $_.ResourceTypes.Locations}

In addition, the releases contain many bug fixes, stability improvements and performance fixes. For the full list of all the changes, refer to the release notes here.


Comments (8)

  1. jackhanbond says:

    Any news on Mesh support for actors? And will meshes be able to span regions? Thanks.

  2. Anonymous says:
    (The content was deleted per user request)
    1. Anonymous says:
      (The content was deleted per user request)
  3. sans_india85 says:

    I could not find information on how to achieve Support for Service Fabric Reliable Volumes that provide high availability through built-in replication. I’m using Visual Studio 2017 and Service Fabric Mesh SDK in Windows 10 V1709, what are the changes I need to do in volume.yaml and service.yaml. Please help/guide.

    1. It seems root level volume resource currently supports AzureFiles only, and then you attach them by VolumeRefs property.
      Application scoped HAVolumes are attached by Volumes property at the Application/Service/CodePackage level. Please check this ARM template: https://raw.githubusercontent.com/Azure-Samples/service-fabric-mesh/master/templates/counter/counter.sfreliablevolume.linux.json

  4. In this post you state: “The new tooling will work against local Service Fabric 6.4 clusters.”

    What does this mean? I’m fairly excited to begin implementing some of the new resource-based functionality in our existing Service Fabric clusters, but any details about how these new features work outside of Service Fabric Mesh are scarce and incredibly vague.

    I’m sure that I’m not the only one who would love more clarity on this topic.

    1. CostasZ says:

      +1 on more details. If anything I would say that hurts SF adoption the most.

    2. It is about local SF sdk, one that runs “local SF cluster” on dev’s pc.
      After installing tooling to VS you will be welcomed with message that your ibstallation of SF sdk also needs to be upgraded to be able to debug and publish.

Skip to main content