Release of SDK 2.6.204 and Runtime 5.6.204 for Windows, and a preview of what’s next

This is an exciting time for Service Fabric. Today we released versions 5.6 of the runtime and 2.6 of the SDK with much anticipated support for Windows Server Containers, making Service Fabric a world-class, production-ready container orchestrator for Windows, with Linux not far behind. You can read more about these new container capabilities on the Azure blog. An update to the Service Fabric Standalone will be released separately at a later time.

We're also announcing a separate preview release of Service Fabric 5.7 that has support for deploying Docker Compose applications to a Service Fabric cluster. The 5.7 Preview is available now in Azure, and the 5.7 Preview SDK will be available for download in the next few days on Web Platform Installer and NuGet. Note that you won't be able to upgrade a cluster that is running the 5.7 Preview, neither from an earlier release version, nor from the preview release to the final release when it's available. For this preview release, we've used a special versioning scheme for the Service Fabric runtime that looks like this: 255.255.5709.255, which is what you'll see when you create a cluster with the 5.7 Preview in Azure:


This same versioning scheme will appear in your installed programs when you install the SDK. The associated preview NuGet packages, however, use the standard 2.7.0-preview versioning scheme you typically see with pre-release NuGet packages.

An update to Visual Studio 2017 tooling for Service Fabric is also available in the Visual Studio 2017 15.3 Preview 1 release, which can be installed side-by-side with the latest stable release of Visual Studio 2017. If you're still using Visual Studio 2015, we've got you covered too with an update to the Service Fabric tools included with the SDK.

Some other highlights of this release include:

New Service Package Activation options

A new exclusive process activation option for service instances creates a dedicated process for each replica of a service. With this new option, you can now choose to use the current shared process hosting model for services instances and replicas, or you can choose to run everything in its own process.

Patch orchestration service

We've released an application that you can download and deploy to your cluster to automate OS patching for your cluster nodes. This application ensures OS updates are automatically downloaded and installed, and the node is rebooted when necessary. This application is integrated into the Service Fabric health system for safe, coordinated patch roll-out, and it works in both Azure clusters as well as standalone clusters.

Reliable Concurrent Queue

The Reliable Concurrent Queue replicated data structure, which provides concurrent producer and consumer functionality with best-effort FIFO ordering, is now out of preview and ready for production use.

DNS Service

Many services, especially containerized services, can have an existing DNS name, and being able to resolve these using the standard DNS protocol (rather than the Naming Service protocol) is convenient, especially in application "lift and shift" scenarios. The DNS service provides DNS resolution for service endpoints running in your cluster.

Reverse Proxy improvements

A number of new features and improvements have gone into the Reverse Proxy, including HTTPS forwarding, client certificate authentication, and support for custom user-defined HTTP verbs.

Certificate revocation list management

This new improvements gives you more control over how certificate revocation list settings and how they're handled by the system to find the right balance between security and availability for your cluster.

As always, be sure to read through the full release notes for a complete list of new features, improvements, and bug fixes.

The Service Fabric Team

Comments (20)

  1. Niels Egberts says:

    I have updated visual studio 2017, updated the nuget packages and updated the SDK, but during deployment with the new setting ServicePackageActivationMode we get an error: “There is an error in XML document (65, 42)”

    The complete setting is like this:

    The line number 65 corresponds to the new setting.

    What are we missing?

    1. ravpal says:

      Niels, Please make sure your service fabric application project is upgraded to version 1.6 and this project is using the NuGet package Microsoft.VisualStudio.Azure.Fabric.MSBuild.1.6.0. This error could happen if the ApplicationManifest.xml is using the new attribute ServicePackageActivationMode that is available from 1.6 tooling , but old version of Microsoft.VisualStudio.Azure.Fabric.MSBuild Nuget package is used by the project. Also make sure the target the cluster version is 2.6 if you are using this new feature.

      1. Niels Egberts says:

        Yes, the nuget package is updated to 1.6. Target local cluster is also updated. I reported the error here also:

  2. Niels Egberts says:

    Since html is not allowed, the line is like this: Service Name=”MyService” ServicePackageActivationMode=”ExclusiveProcess”

  3. Nick Trentacoste says:

    Can you provide a link to the updated Standalone Setup package with the new bits? The download from the docs site still points to 5.5.

    1. The StandAlone version has not yet been released. Once it is available we will make an announcement of its release on this blog.

  4. Nick Trentacoste says:

    Nvm, I just re-read the article and see that it states the standalone will be released at a later time. Am I able to upgrade my applications to latest while leaving the fabric at the previous version?

    1. No. The apps cannot be bound to a higher version of the runtime than what is running on the cluster. I suggest you wait.

      1. Steven Bense says:

        Please could we get an ETA on the update to the standalone 5.6 update components? Thank you.

  5. Could you please share the link to the mentioned patch orchestration service. Thank you!

    1. The patch orchestration application will be available end of this week or early next week. We had to pause its rollout, for the Build Conf and now have restarted it. We will make an announcement of its availability on this blog.

  6. Bal Purewal says:

    Where can I download the stand alone setup package for 5.6? still points to 5.5

    1. The StandAlone version has not yet been released. Once it is available we will make an announcement of its release on this blog.

  7. JonDoe2 says:

    I am try to upgrade a cluster currently running but Get-ServiceFabricRuntimeUpgradeVersion doesn’t return any newer versions? How do I upgrade to the latest version?

    1. Matt Snider [MSFT] says:

      I presume that’s for the standalone version of SF, which I don’t think we’ve published the packages for yet.

      1. Matt Corr says:

        Any idea when the CAB files will be released for 5.6.210? We are hoping to creating our multi server Service Fabric cluster using the current version, and it seems we are not able to until these CAB files are released.

        Please let me know if there is an alternative approach?

  8. Jan Modaal says:

    Where can we download this `Patch orchestration service` application?

    1. @JanModaal – The patch orchestration application will be available end of this week or early next week. We had to pause its rollout, for the Build Conf and now have restarted it. We will make an announcement of its availability on this blog.

  9. GS says:

    Will new blog be created or any other sort of notification released when standalone package will be available for 5.6?

  10. I have a 2.6 project and needed to reinstall my machine. I reinstalled vs2017. On opening the project, I receive the message “this project type requires Microsoft Azure Service Fabric SDK version 2.5 or higher”. I tried installing the SDK from the Web Platform Installer but it won’t install due to vs2015 not being available.

    Is the implication of comments in this blog post that this can’t be resolved until the stand alone installer is available? i.e. you must have vs2015 installed. Seems like that should be called out if so.

Skip to main content